Drupal Answers is a question and answer site for Drupal developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working in Drupal 6.x. I have approximately 50 content types. All content types have common fields CCK. Each content type has approximately 25 fields. Is better share the common fields CCK or is better to make the fields for each content type?

These content types are used for views.

In terms of performance, resource consumption, what is the better option?

Thanks to all for your ideas.

share|improve this question
I'm not sure about your question, but if a lot of your content types are very similar, you might want to use taxonomy to separate them. This way you have fewer content types, and you can still use views by filtering on taxonomy terms. The UI would probably be easier to create an "Automobile" and tag it as a type "Car" than scrolling through a list of content type to create a "Car" directly. Just some thoughts. – bkildow Sep 20 '11 at 14:52
Looks like this is a duplicate of drupal.stackexchange.com/questions/10990/… – landing Sep 20 '11 at 22:45
@landing I disagree, I think that could not be related, someone can have several content types and some of this content types without CCK fields. – cigotete Sep 22 '11 at 20:24
@moon.watcher I guess the question I linked to isn't really a duplicate, but the answers provided may have some insight into site performance when it comes to using a lot of cck fields with views. Credit to David Meister for pointing out that building a view to output shared fields will make your queries less efficient. – landing Sep 22 '11 at 20:54
@landing yes, I agree, there are answers related. – cigotete Sep 22 '11 at 21:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.