The Stack Overflow podcast is back! Listen to an interview with our new CEO.
3 edited tags
| link
2 Correct spelling
source | link

Why does Drupal storesstore each custom field in a separated table?

I understand that, in order to add functionality to nodes and node types, extra fieldfields must be created in the database. 

Now, I don't see why a one-field-one-table schema is used instead of favouring the schema of just a single table for a content type, and then, in that additional table, all the extra fields. What are the adventages of that approach? 

I have a site with 1,000+ tables and is being a mess to administer.

Why does Drupal stores each custom field in a separated table?

I understand that, in order to add functionality to nodes and node types, extra field must be created in the database. Now, I don't see why a one-field-one-table schema is used instead of favouring the schema of just a single table for a content type, and then, in that additional table, all the extra fields. What are the adventages of that approach? I have a site with 1,000+ tables and is being a mess to administer.

Why does Drupal store each custom field in a separated table?

I understand that, in order to add functionality to nodes and node types, extra fields must be created in the database. 

Now, I don't see why a one-field-one-table schema is used instead of favouring the schema of just a single table for a content type, and then, in that additional table, all the extra fields. What are the adventages of that approach? 

I have a site with 1,000+ tables and is being a mess to administer.

    Tweeted twitter.com/StackDrupal/status/702792919611273216
1
source | link

Why does Drupal stores each custom field in a separated table?

I understand that, in order to add functionality to nodes and node types, extra field must be created in the database. Now, I don't see why a one-field-one-table schema is used instead of favouring the schema of just a single table for a content type, and then, in that additional table, all the extra fields. What are the adventages of that approach? I have a site with 1,000+ tables and is being a mess to administer.