[development] One-to-one tables considered harmful

FGM fgm at osinet.fr
Mon Jun 4 06:30:44 UTC 2007

It seems to me you might be over-generalizing. Do you have any data to back
up this assertion (URL ?) ? From what I remember from examining Firebird and
Oracle query plans, they can apply criteria on several tables in a join
without significantly impacting performance.

----- Original Message ----- 
From: "David Strauss" <david at fourkitchens.com>
To: <development at drupal.org>
Sent: Monday, June 04, 2007 8:19 AM
Subject: Re: [development] One-to-one tables considered harmful

There is no debate here, no matter what theoretical model you prefer.
The database requires that all criteria for WHERE and ORDER BY exist in
the same table to achieve acceptable performance. That table is {node}.
The only way to realize the same performance goals without combining the
fields in {node} is to create another table that contains the same
fields, but just isn't called node. That would be pointless.

More information about the development mailing list