Closed (fixed)
Project:
Content Construction Kit (CCK)
Version:
6.x-2.x-dev
Component:
upgrade path
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 Jan 2008 at 20:36 UTC
Updated:
25 Nov 2008 at 02:11 UTC
This issue is for the db_field_set_no_default(); problem when updating a field from Drupal 5, as outlined in http://drupal.org/node/198502#comment-664981 and http://drupal.org/node/200359#comment-664993 .
Essentially, dropping the DEFAULT appears to be breaking the ability to do INSERTs on content_field_* tables without explicitly stating a value or defining a DEFAULT value.
Comments
Comment #1
yched commentedMoving the issue to the (newly created) 'upgrade path' component. I fear these deserve a category of their own :-/
Comment #2
fractile81 commentedComment #3
karens commentedBringing this forward. Is this still an issue?
Comment #4
yched commentedAssuming fixed by now