DB Schema update

[manderg]

Hi,

I´m upgrading my version and when I test the config i get the following:

Check DB config
DSN (write):  OK
DB Schema:  NOT OK(Database schema differs)

    Schema version: 2020020100 (required: 2019092900)



Does anyone know what 2020020100 relates to in the list of version to update from?

Thanks,

Graham

[JohnDoh]

That message suggests you are currently using database schema version 2020020100 - so you are running an old git master version of Roundcube? And you are trying to downgrade to version 1.4.x (thats the required bit)?

Version 1.4.0 of Roundcube shipped with database schema version 2019092900.
Version 1.5.0 of Roundcube shipped with database schema version 2020122900.

You are currently running something in between and the only way to get that is from git-master. As far as I know there are no supported downgrade paths for Roundcube, not with the installer any way. So your only option would be to update to version 1.5.2 (current stable) rather than downgrade to the 1.4.x series.

[manderg]

Hi,

I started off with 1.3.10 (before that not sure) and then went to 1.3.17. I tried going direct to 1.5.2, but it wouldn't have it, via the upgrade script, no worries. So I have updated from 1.3.17 to 1.4.13, which is what the screenshot is from.

The question I have is, what version should i choose in the drop-down, to update from? As I tried 0.9 or newer and it gave an error...

Thanks,

[JohnDoh]

I tried going direct to 1.5.2, but it wouldn't have it, via the upgrade script

So you attempted to upgrade to 1.5.2 and it failed. I'm guessing you had a database error, the upgrade script updated your database up to 2020020100 and then failed on 2020020101?

Really the 2020020100 is not a big one and will still work fine with 1.4.13 I think but you could revert it back to 2019092900 with:

Code: [Select]

ALTER TABLE `users` MODIFY `language` varchar(5);
ALTER TABLE `dictionary` MODIFY `language` varchar(5) NOT NULL;
UPDATE `system` SET `value` = 2019092900 WHERE `name` = 'roundcube-version';


[manderg]

Thanks for the info. My host is going to upgrade the version of MySQL soon, so this should fix the errors when going to a new version.