Drupal Database Structure - Efficient/Inefficient?

Question

I\'m certainly no Drupal expert, but I\'ve schemed and built a few databases before, so am puzzled by the structure of a database a 3rd party team is working on that I had S

Answer 1

Yes. Drupal stores field content in individual tables so that it will be maximally flexible (for example, if you wanted to re-use those fields on other content types besides "organization" later), it is already in a multi-join table. The tradeoff is performance, which Drupal makes up for with caching and such (for example when that Organization node is loaded, it caches it so that if it's loaded again in that page request it doesn't need to read from those tables again, for example). Since it's a powerful CMS that lets you build and re-build and reorganize how you store your content and fields, it stores the data more flexibly.