After upgrading from D5 to D6 and inspecting the schema, there is a mismatch between what D5 setup and what the D6 schema says.

  • column sid:
    declared: array('type' => 'serial', 'not null' => TRUE)
    actual: array('type' => 'int', 'not null' => TRUE, 'default' => 0, 'disp-width' => '10')
  • column sid:
    declared: array('type' => 'serial', 'not null' => TRUE)
    actual: array('type' => 'int', 'not null' => TRUE, 'default' => 0, 'disp-width' => '10')

I started to update my database manually to add the auto_increment to the sid column that would turn it into serial, but I'm pretty sure serial on sid is a bad thing. MySQL reinforced that thought because it wouldn't let me declare sid a primary index that would be needed to make it auto_increment. My understanding is that sid references state ids from the workflow_state table, which can and should be repeated in the workflow_access table.

Comments

Bastlynn’s picture

Bastlynn commented
Status: Active » Closed (won't fix)

I believe this has been fixed since this was noted over 2 years ago. (You're right, adding serial on that table would not be smart.) If not please open a new request and reroll a patch against D7, since that's where we're trying to move this module at this point.