upgrading problems with database

Next topic

Author	Message
Erland Flaten	Friday 05 June 2009 5:29:42 am I have, to my surprise, managed to upgrade from 401 to 403. The database controll shows no errors, but fileconsistency shows: Warning: it is not safe to upgrade without checking the modifications done to the following files: autoload/ezp_extension.php Everything looks fine as far as I can see. When I continue my expedition into the holy land of 4.1 I get a mysql error when I paste and run the db upgrade commands from the mysql/4.1/dbupdate-4.0.0-to-4.1.0.sql -- START: from 4.0.1 ALTER TABLE ezcontent_language ADD INDEX ezcontent_language_name( name ) ; MySQL sa: #1061 - Duplicate key name 'ezcontent_language_name' I guess the upgrad procedure I use above is the correct one as there is no 4.03 to 4.12 .sql file. Is there some sql files in 4.04 and 4.05 I have tu run? is 403 to 412 to the right path anyway? Erland Flaten Lilllehammer, Norway
Łukasz Serwatka	Friday 05 June 2009 5:41:36 am You don't have to pay much attention to the autoload/ezp_extension.php. It is quite natural that file change when new extensions are enabled. md5 sum checkup should be skipped for that file. If you have any custom extension then it is good idea to re-run autoload updater after upgrade. Reg. to SQL calls, you can omit queries when the indexes already exists. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Erland Flaten	Friday 05 June 2009 6:23:53 am Thanks: ) Issuing the last sql coomands in the file 411 to 412 I got another error I hope doesent matter too much. Error SQL-spørring: ALTER TABLE ezsession ALTER COLUMN user_hash SET DEFAULT ''; MySQL sa: #1054 - Unknown column 'user_hash' in 'ezsession' Erland Flaten Lilllehammer, Norway
Gaetano Giunta	Saturday 06 June 2009 5:33:10 am The missing column is most likely due to some incomplete /missing sql upgrade scripts. I see it is part of dbupdate-4.0.0-to-4.1.0.sql, so my guess is that you did not run succesfully all of it (from your previous post). I think you should then try to run again the dbupdate-4.0.0-to-4.1.0.sql script, a statement at a time, ignoring all the ones that fail due to stuff having already been done Principal Consultant International Business Member of the Community Project Board
Erland Flaten	Tuesday 09 June 2009 6:33:42 am I have now a up and running version of my site in version 4.1.2 Running the 4.0.0-4.1.0 sql commands one at a time in phpmyadmin solved it. I will of cource continue with 4.1.3 localy on my mac before I do this scary stuff on the webserver. Thanks :) Erland Flaten Lilllehammer, Norway