[support] CCK fields being created as separate tables in the db

[Neil: esl-lounge.com]

OK, I found the answer in the second half of this article on the db aspects of CCK:

http://www.lullabot.com/articles/an_introduction_to_the_content_construction_kit

the two fields (which were actually hobbies and favourite music genres now I recall...) both accepted multiple values so it seems that is the crucial factor in deciding whether a CCK field gets added to the db as a separate table or part of a content type table: that - and whether the field is shared between content types.

Neil
  ----- Original Message ----- 
  From: Neil: esl-lounge.com 
  To: support at drupal.org 
  Sent: Friday, March 21, 2008 10:16 AM
  Subject: [support] CCK fields being created as separate tables in the db


  I've been pulling my hair out about this for two hours. I have made a nodeprofile content type and am using cck fields to build it.

  All the fields I created were added as columns to the content_type_nodeprofile table....except the last two which were added to my db as separate tables:

  content_field_hobbies
  content_field_age

  these were the last two I added and, also, I had a few problems with the "group" they sat in, so I ended up changing the name and deleting and recreating the groups at least once...may this have caused the issue? 

  I've tried totally deleting the relevant fields and groups and starting again, but they keep getting created as separate tables. Aagh!!

  Basically, what is it that makes CCK create a field as a separate table instead of putting it as a column inside the content type table?

  Neil



------------------------------------------------------------------------------


  -- 
  [ Drupal support list | http://lists.drupal.org/ ]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20080321/5a570d96/attachment.htm