Update from 3.0.0 to 3.2.0 without data loss

[simonbaev]

Issues: Cannot restore DB dumped on 3.0.0 onto 3.2.0

Steps to get the error msg:
1. Dumped MySQL DB on 3.0.0 using

Code:

mysqldump -u<user> -p <dbname> > dumpfile.sql

2. Installed (extracted SVN archive) 3.2.0 into separate directory on the webserver.
3. Created new DB (letodms32) with dedicated user (letodms32) user and granted permissions with respect to Step 5. on http://www.letodms.com/doc/doku.php?id=install:install
4. Customized conf/settings.xml
5. Loaded <letodmsIP>/install into browser, filled out form fields, check marked "Create DB" and ran the process. Received confirmation on successful installation.
6. Tried to use admin/admin account -- works fine.
7. Dropped DB, i.e. letodms32, populated automatically on Step 5 and repeated Step 3. to create empty DB.
8. Restored dumped DB from 3.0.0. installation by running

Code:

mysql -u letodms32 -p letodms32 < dumpfile.sql

(the dump file was prepared on Step 1).
9. Tried to open letoDMS in browser -- received error message stating that DB needs to be updated, i.e. "Database update needed" (as expected).
10. Executed

Code:

mysql -u letodms32 -p letodms32 < UPDATE-v3.1.0/update.sql

No error message was displayed.
11. Repeated Step 9. -- failed with the same error, i.e. "Database update needed".
12. Tried to repeat Steps 7,8 followed by

Code:

mysql -u letodms32 -p letodms32 < UPDATE-v3.0.0/update.sql

Got error "ERROR 1054 (42S22) at line 1: Unknown column 'isAdmin' in 'tblUsers'"

Error msg: see above description of the problem.

LetoDMS Version: 3.0.0, 3.2.0

PHP version: 5.2.6-1+lenny13 (title of the table generated by phpinfo())

MYSQL Version : 5.0.51a-24+lenny5 (output of mysqldump)

Windows or Linux Server: Debian Lenny 2.6.32-5-686-bigmem

Question: Is there any working procedure to upgrade from 3.0.0 to 3.2.0?

Thank you.

--
Simon

[steinm]

Question: Is there any working procedure to upgrade from 3.0.0 to 3.2.0?

Everything you did was quite ok, there is just one thing I missed in the upgrade process.
The database contains a table tblVersion which holds the current version. This must
match the version of LetoDMS. If you set the field 'minor' to 2 it should work.

Uwe

[simonbaev]

The database contains a table tblVersion which holds the current version. This must match the version of LetoDMS. If you set the field 'minor' to 2 it should work.

It Worked! But I can see "LetoDMS, 3.1.0-RC1" in Admin-Tools-> Version Information... It was expected to be 3.2.0 as taken from the SVN.

Also I don't have clear understanding how DB and DataLocation are connected to each other. Definitely there should be some level of consistency in terms of DB to reflect real directories and files stored at DataLocation. What if I'd like temporally run two versions of LetoDMS 3.0.0 (as production environment) and 3.2.0 (for experiments)?

My intend is to do the following:
1. Clone DataLocation directory from the production environment to some other location.
2. Create "staging" and "lucene" subdirs in there
3. Point cloned directory and two of its subdirs (created on Step 2) from conf/settings.xml
4. Clone DB from the production environment according to my previous post and modify Minor version to 2 from 0.

Would these steps be enough for safe transition and making separate installation of the 3.2.0 which won't affect the production environment, namely 3.0.0?