While updating from the 6.x-1.0 version to the 6.x-1.x-dev version I just checked out from the CVS, I get the following errors upon running update.php

    * warning: Invalid argument supplied for foreach() in /(web directory)/httpdocs/includes/database.mysql-common.inc on line 69.
    * user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') /*!40100 DEFAULT CHARACTER SET UTF8 */' at line 2 query: CREATE TABLE cache_nodewords ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /(web directory)/httpdocs/includes/database.inc on line 517.
    * user warning: Duplicate column name 'enabled' query: ALTER TABLE nodewords_custom ADD `enabled` TINYINT NOT NULL DEFAULT 1 in /(web directory)/httpdocs/includes/database.mysql-common.inc on line 298.
    * user warning: Table 'drupal6.cache_nodewords' doesn't exist query: DELETE FROM cache_nodewords in /(web directory)/httpdocs/includes/cache.inc on line 172.
    * user warning: Table 'drupal6.cache_nodewords' doesn't exist query: DELETE FROM cache_nodewords in /(web directory)/httpdocs/includes/cache.inc on line 172.

On update #6120, adding "enabled" to "nodewords_custom" fails because it already exists (size set to 4, I hope this is correct)

Failed: ALTER TABLE {nodewords_custom} ADD `enabled` TINYINT NOT NULL DEFAULT 1

On update #6114, creating the "cache_nodewords" table appears to fail due to some syntax error in the code.

Failed: CREATE TABLE {cache_nodewords} ) /*!40100 DEFAULT CHARACTER SET UTF8 */

I've gone in and manually created the cache_nodewords table by copying the schema from one of the other cache tables, and things appear to be working fine.

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

For the cache table creation error, see #560222: Error after upgrading; the issue report contains a patch that resolves the problem.
For the field enabled size, TINYINT is 1 byte in MySQL; 4 bytes are too much for a field that is supposed to contain just two values (1 for enabled, 0 for disabled).

I will commit a new development snapshot after I will fix another issue (for which I am waiting the feedback of other people).
I apologize for the delay in resolving this problem, which is also caused by the fact I was changing the module code to increase its performance (and make the module API more stable).

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

I committed the fixed code.

Thanks for your report.

Status: Fixed » Closed (fixed)

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