DB error on updating from latest D5 version to D6
esllou - June 19, 2009 - 04:21
| Project: | Printer, e-mail and PDF versions |
| Version: | 6.x-1.7 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I was on latest D5 version and I just upgraded to D6 and got this:
* user warning: Table 'print_node_conf' already exists query: CREATE TABLE print_node_conf ( `nid` INT unsigned NOT NULL, `link` TINYINT unsigned NOT NULL DEFAULT '1', `comments` TINYINT unsigned NOT NULL DEFAULT '1', `url_list` TINYINT unsigned NOT NULL DEFAULT '1', PRIMARY KEY (nid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in C:\xampp\htdocs\includes\database.inc on line 515.
* user warning: Table 'print_page_counter' already exists query: CREATE TABLE print_page_counter ( `path` VARCHAR(128) NOT NULL, `totalcount` BIGINT unsigned NOT NULL DEFAULT 0, `timestamp` INT unsigned NOT NULL DEFAULT 0, PRIMARY KEY (path) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in C:\xampp\htdocs\includes\database.inc on line 515.why was it trying to create two tables that already existed from the 5.x version?
Is that the only meaning of this error message...nothing else to worry about?
#1
they are warnings not errors. The module should probably add a check during update but ultimately this shouldn't be anything to worry about.
#2
That's a problem with the way I maintain this module and the way the Drupal update system works.
I keep the versions in sync, so update 5303 is exactly the same as update 6003. However I would have to find a way to tell Drupal to not apply 6003 if 5303 has already been applied (maybe actively checking for the last update version).
I'll see what I can do, but no promises. It's mostly irrelevant anyway as you've pointed out.
#3
Just set a variable in the 5.x version and check for (and perhaps delete) it in the 6.x version. That's how core handles stuff like that.
#4
That seems strangely complicated. Can you provide an example of where core is doing that?
#5
I have added some code to the 6.x updates to detect the last 5.x module update.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.