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

yched’s picture

Moving the issue to the (newly created) 'upgrade path' component. I fear these deserve a category of their own :-/

fractile81’s picture

Component: General » upgrade path
karens’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev

Bringing this forward. Is this still an issue?

yched’s picture

Status: Active » Fixed

Assuming fixed by now

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.