db update from 1.0-rc4 to 1.0 failed

What database are you using, MySQL or PostgreSQL? What version of the database?

Was this installation of workflow upgraded from version 5.x or was it newly installed for 6.x?

Ditto for me too.

Here's my output. The problem is missing {} brackets in SQL statements, so the table names aren't rewritten for the table names that are actually in use. Interspersed are my suggested fixes.

* user warning: Table 'hfn_dev_share.workflows' doesn't exist query: SHOW COLUMNS FROM workflows WHERE field = 'wid' and extra REGEXP 'auto_increment' in /var/www/hfnetwork-dev/sites/all/modules/workflow/workflow.install on line 403.

Suggested: $workflows = db_result(db_query("SHOW COLUMNS FROM {workflows} WHERE field = 'wid' and extra REGEXP 'auto_increment'"));
Rather than: $workflows = db_result(db_query("SHOW COLUMNS FROM workflows WHERE field = 'wid' and extra REGEXP 'auto_increment'"));

* user warning: Table 'hfn_dev_share.workflow_states' doesn't exist query: SHOW COLUMNS FROM workflow_states WHERE field = 'sid' and extra REGEXP 'auto_increment' in /var/www/hfnetwork-dev/sites/all/modules/workflow/workflow.install on line 404.

Suggested: $workflow_states = db_result(db_query("SHOW COLUMNS FROM {workflow_states} WHERE field = 'sid' and extra REGEXP 'auto_increment'"));
Original: $workflow_states = db_result(db_query("SHOW COLUMNS FROM workflow_states WHERE field = 'sid' and extra REGEXP 'auto_increment'"));

* user warning: Table 'hfn_dev_share.workflow_transitions' doesn't exist query: SHOW COLUMNS FROM workflow_transitions WHERE field = 'tid' and extra REGEXP 'auto_increment' in /var/www/hfnetwork-dev/sites/all/modules/workflow/workflow.install on line 405.

Suggested change: {Ditto}.

It looks like the following are just failures caused by the missing{}'s above.

* user warning: Incorrect table definition; there can be only one auto column and it must be defined as a key query: ALTER TABLE share_workflows DROP PRIMARY KEY in /var/www/hfnetwork-dev/includes/database.mysql-common.inc on line 386.
* user warning: Multiple primary key defined query: ALTER TABLE share_workflows CHANGE wid `wid` INT NOT NULL auto_increment, ADD PRIMARY KEY (wid) in /var/www/hfnetwork-dev/includes/database.mysql-common.inc on line 520.
* user warning: Incorrect table definition; there can be only one auto column and it must be defined as a key query: ALTER TABLE share_workflow_states DROP PRIMARY KEY in /var/www/hfnetwork-dev/includes/database.mysql-common.inc on line 386.
* user warning: Multiple primary key defined query: ALTER TABLE share_workflow_states CHANGE sid `sid` INT NOT NULL auto_increment, ADD PRIMARY KEY (sid) in /var/www/hfnetwork-dev/includes/database.mysql-common.inc on line 520.
* user warning: Incorrect table definition; there can be only one auto column and it must be defined as a key query: ALTER TABLE share_workflow_transitions DROP PRIMARY KEY in /var/www/hfnetwork-dev/includes/database.mysql-common.inc on line 386.
* user warning: Multiple primary key defined query: ALTER TABLE share_workflow_transitions CHANGE tid `tid` INT NOT NULL auto_increment, ADD PRIMARY KEY (tid) in /var/www/hfnetwork-dev/includes/database.mysql-common.inc on line 520.

To anyone having the same error: in my case the database format was correct: my original fresh install of rc4 had the right structure, and these errors didn't leave the database in a bad state. Fixing the code just meant that the it didn't generate any errors.

I've committed the fix to add curly brackets and the change will appear in 6.x-1.1.

However, it seems that the SQL is not compatible with MySQL 4. It looks like we will need a different way to check if wid is an autoincrement field that works in MySQL 4.

I have the same SQL syntax problem with SQL4 as the one you mention above (autoincrement field check). Does this affect the functionning of workflow on D6. Did anybody find a solution ?

Thanks for your answers.

Regards.

Since this request is over 2 years old, I'm going to assume a solution was found or you've moved on. If not, please get updated to the latest versions of all modules and see if things have fixed themselves. If not, open a new ticket and I'll be glad to look at it.