Greetings,
I have a field 'description' and I would like to add description to content types 'event' and 'room'. I want to receive two tables node_event and node_room each of which will have a column 'description'.
Here is an inconvenience I've met when using one field for 2 content types - it is impossible to create two fields with the same name for different node types. When I'm trying to use feature 'add field from the list of existing ones' CCK create a new table node_data_field_description instead of adding description column for node tables.
I consider this to be an inconvenience.
node_data_field_ table is needed only when field is multiple. In the situation I described both description fields are NOT multiple. Creating 'event_description' and 'room_description' fields is not good. I also think that every field should be unique only within one content type.
It is inconvenient when creating custom modules where we need to execute our own specific queries upon tables created by CCK. Of course we can use JOINS but why not to get rid of superflous relations?
What do you think about this?
Thank you.
Comments
Comment #1
snobojohan commentedIf you use "Add existing field" insted on "create new filed" it shold work. No?
Comment #2
ardas commentedNo. As I said before even if I add an existing field it creates a field table just like for multiple field.
In the situation I've described we don't have multiple fields, instead we have 2 single fields for 2 different node types with the name. To force them to be created in node tables we have to give them unique names just like 'event_description' and 'room_description' which is not good.
Comment #3
karens commentedA very old feature request for D5, won't do anything with this now.