[development] Is it possible to have separate table for different content types in D7
steven.jones at computerminds.co.uk
Fri Feb 11 17:53:56 UTC 2011
If you are trying to store all your field data (additionally) in a one
table (where possible) then you may be interested in:
This will then use as few joins as possible when doing selects, but
data is written to two places, so you have to take the hit on writes.
ComputerMinds ltd - Perfect Drupal Websites
Phone : 024 7666 7277
Mobile : 07702 131 576
Twitter : darthsteven
On 11 February 2011 17:50, nan wich <nan_wich at bellsouth.net> wrote:
> JOINs, for the most part, are not bad. "Lots of ... fields" may be more the
> issue. It might be a good time for rethinking the design. You do have a
> design document, don't you? This may be a case where a custom node module
> (single query without JOINs) may be a better choice. Or a faster CPU with
> more memory... Also get a DB expert to tune the DB settings for this set up.
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
> From: Deva
> In my case i am going to have lots of content types with lots of cck fields.
> D7 creates new table for each cck field. So while reading a node from
> database. It is going to do a join. I dont think that is good thing.
> That is why i was checking if it is possible to have different table for
> each content type.
More information about the development