Your database is out-of-date ... schema migrations

denbell

I've upgraded to the latest trunk version, and now when I go to the site I get the dreaded "Your database is out-of-date" screen, so I've read through the Upgrade/Migration page that is referred to. And I can't understand the second half of the process, where I need to update the database schema. I am quite a novice when it comes to shell commands.

mysql -v -v -u collective_acces -p -h localhost collective_access < support/sql/migrations/7.sql

Is that command only usable through SSH? I cannot connect to my server via SSH on my shared host, so is there a way to do this via php MyAdmin? In the sample command, what is the "collective_acces" that is referred to, is that the database name? Why is it spelled with an absent "s" in the two versions?

For now, my site is down because of the upgrade. A little more detailed step-by-step instructions would help me get my site back online, I'd appreciate it. Has anyone else run into this issue?

seth

Hi,

At the present time database updates need to be done manually by loading migration files into your MySQL database. These files are numbered and located in support/sql/migrations

You can load the migration files using the MySQL command line (usually via an SSH session), or you could copy and paste the files into a web-based tools like PHPMyAdmin and run the SQL directly. Migration files are just plain old SQL commands so it doesn't matter how they get executed by the database so long as they do. Given that you do not have SSH access, PHPMyAdmin is the way to go. Just copy the content of each file into the SQL window, execute it as a query and you should be good. Be sure to paste the entire file as there are multiple queries in most of them.

The 'collective_acces' reference on the wiki is a typo. I just fixed it.

An automatic method for applying migrations is long overdue, and I apologize for the hassle this is causing you. We just received a contributed patch that implements automatic application of migrations a few days ago. We're looking it over carefully right now. It almost certainly will not make the 1.0 release as we want to test it thoroughly, and there isn't enough time before 1.0. I expect it'll go into the dev branch in a week or two, and into trunk within a month.

seth

denbell

well, that was certainly a fast and simple fix, once I understood! Thanks for clarifying. It only took a couple minutes to fix it. I copied the contents of each file in order as you suggested, pasting them into the PHPMyAdmin window and by the end, everything is fine, back online, and functioning as well as ever … well, probably better because of the upgrade.

Thanks for the superfast response Seth, and maybe this thread will help someone else who had a similar issue.