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. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
________________________________ 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.
