I got the following syntax error when enabling the module:
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 'falsekwh decimal(10,2) NOT NULL default 0,enableco2 tinyint(1) query: CREATE TABLE carbon_footprint (nid int(10) unsigned NOT NULL default 0,postcode varchar(10) NOT NULL default '',organization varchar(40) NOT NULL default '',model varchar(20) NOT NULL default '', firstdate int(11) NOT NULL, enablekwh tinyint(1) NOT NULL default falsekwh decimal(10,2) NOT NULL default 0,enableco2 tinyint(1) NOT NULL default trueco2 decimal(10,2) NOT NULL default 0,filing_status int (2) NOT NULL default '0',protection int(2) NOT NULL default '0',PRIMARY KEY (nid)) in includes/database.mysql.inc on line 121.
Not sure whether that's serious or not!
Drupal: 4.7.4
Carbon: carbon.module,v 1.12 2007/01/30 20:19:33 johnackers Exp $
Comments
Comment #1
dbassendine commentedI'm also getting
user warning: Table 'zamama_cration2.carbon_footprint' doesn't exist.Comment #2
john ackers commentedApologies. New install had not been tested. There are spaces missing at the ends of the recently added lines. Please wait for an overnight build or take
this version of carbon.install from CVS,
Comment #3
dbassendine commentedThanks, John.
That solves the error message when enabling, but the install still doesn't create the carbon_footprint table i.e. I get
user warning: Table 'zamama_cration2.carbon_footprint' doesn't existwhen going to admin>carbon_footprint.Actually, no carbon_* tables are getting created, it seems!
Comment #4
john ackers commentedIt sounds like Drupal thinks the install was successful. In fact the carbon.install functions afaik cannot indicate that the install previously failed.
I would run these two lines of SQL
The first line uninstalls the carbon module and deletes information about the current schema.
Then reenable the module. The install will be reattempted. Hope this works. Sorry you are having this problem as a result of my bug.
Comment #5
dbassendine commentedFine now, thanks. No worries!
Comment #6
(not verified) commented