Closed (fixed)
Project:
Content Construction Kit (CCK)
Version:
6.x-1.x-dev
Component:
content.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 Apr 2006 at 16:29 UTC
Updated:
12 May 2006 at 14:16 UTC
I get
Warning: Unknown column 'delta' in 'field list' query: INSERT INTO node_content_...
every time when I submit a node with multiple-values field.
I use latest CVS and standard text field.
After form submit I see that the data have ['delta'] in both 'single' and 'multiple' cases. That's good because IMO field switching from 'multiple' to 'single' (and back) must keep all "delta's" data at least for next submission to make at least 1 'undo'. Or please make a dialog to confirm this switch if You sure that this cannot be undone.
Thank You!
Comments
Comment #1
karens commentedI'm also having all kinds of problems trying to use multiple value fields. If I'm reading the code correctly it looks like when I create a multiple value field it should be creating a node_date_field_name table (with a delta column) to store the extra values in, but no such table is being created. Then when I try to save a multiple value field it tries to put the data, including the delta value, into the node table (which has no delta column) instead of the field table and generates a sql error. So I see at least 2 problems, it is not recognizing the right table to use for the insert/update and the table is not getting created when I create or change a field to multiple values.
Using latest cvs (today). Trying to create fields, fill them, then change them from single to multiple values. Have tried number and nodereference fields, it looks like the problem is with all types.
Comment #2
jonbob commentedI believe this is fixed now. The table structure was not being changed correctly when a field was set to and from accepting multiple values. The error at insert time was a side-effect of this.
Affected fields may have to have multiple values turned off and then back on to have the table structure corrected.
Comment #3
karens commentedDownloaded the latest cvs just now and can confirm that it works. It does seem to need some toggles on and off to get it working. A FYI for anyone else doing this, I lost data in nodes that I updated when it was not working right, not just for the field I was trying to change but other fields, too, so DO NOT UPDATE any fields until you can see that the new tables have been created or test it by creating a new record rather than trying to update an existing one.
Comment #4
(not verified) commented