I chose Drupal 6 because the structure of the database for custom content types was closest to our data model, albeit with the centralised Node table added. It works better in terms of normalisation and in terms of our system this was vitally important to us. We have been building logical data models for 30 years and the idea of doing everything from the front end and using the hideously convoluted views method to pull out data in awful SQL queries makes little sense to us.
Anyway, point being that the data model is still extremely important to us, but we are aware that the need to upgrade to Drupal 7 is going to get ever more urgent. My question is whether it is possible to keep a similar data structure, or whether you have to use the method that Drupal has adopted for its database in its core CCK module. The idea of having a table for each field, as I understand is the case, is so completely absurd to me that it makes me a bit nauseous. If I'm wrong, please correct me because I would love to be wrong about this.
So is there any way I will be able to upgrade my system and keep a relatively similar data structure, whilst still leveraging the advantages to using the Node system? I've avoided similar problems in d6 by making sure never to use the apparently useful feature to share fields across different content types. Something else which makes me shudder slightly...
BTW I do really like Drupal, honest