Am 2013-03-13 16:24, schrieb Peter Schmidt: > Hi! > > I was happily using SOGo 1.3.12c (I use it for now only to be > independent from Google for syncing my contacts and calendars and as a > playground for future installations). > > I decided to upgrade to 2.0.4b-1 via aptitude now and all worked like a > charm. > > Then I ran the sql-upgrade scripts and made a mistake (because to me the > naming and documentation is not so clear): > > I ran the sql-update-1.3.16_to_1.3.17-mysql.sh script, instead of the > sql-update-1.3.11_to_1.3.12-mysql.sh, which I think I should have ran > first. > > Now when I try to run the latter one, I get an Error: > ERROR 1068 (42000) at line 1: Multiple primary key defined > > Does this mean, that my DB is already broken, or are the scripts > supposed to be run when the version was below the ones given in the > filename? As I said, to me the naming of the files and documentation in > the userguide is not so clear. > Are the section titles n chapter "Upgrading" - e.g. "1.3.17" - meant > like "Upgrading FROM 1.3.17" or "Upgrading to 1.3.17" - because the > first paragraph says "...when upgrading to the current version...", so I > would read it as "upgrading FROM 1.3.17". > > Is there a way to check the integrity of the database? > > My suggestion to ease the handling of database upgrades in the future: > Adding a version table that keeps track of the db structure upgrades > would allow checking of the validity of an update and would therefore > allow db-auto-update scripts. This is a widely accepted best practise > anyway. >
As you already have a 1.3.12 version of SOGo, you do not use sql-update-1.3.11_to_1.3.12-mysql.sh at all!!! Running sql-update-1.3.16_to_1.3.17-mysql.sh is all you have to do. Kind regards, Christian Mack -- Christian Mack Gruppe Informationsdienste Rechenzentrum Universität Konstanz -- users@sogo.nu https://inverse.ca/sogo/lists
