-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from 1.3.0 to 1.3.3 failed "Error in DDL upgrade" #6034
Comments
Did you have an older version before 1.3.0? That DDL file exists since 1.3-beta, so I don't see a reason it was executed now. Maybe |
I'm using roundcubemail since 1.1.0. Each time it was necessary i upgraded my roundcubemail. Today i want upgrade from 1.3.0 to 1.3.3. How can i display full upgrade log ? "logs" folder is empty |
I was talking about the installto.sh script output. |
Here is a full upgrade log from 1.3.1 to 1.3.3
|
I think that might be caused by some earlies upgrades. Could you check |
You are right: the select statement returned "2016100900". |
I'm closing this ticket as you're the only user with such an issue. I don't know how that could happen, but your problem with privileges tells us that maybe you did something wrong on database setup. As I said, 1.3.0 (or 1.3.1) should have '2016112200' version in database, in such a case the upgrade will not error out, because it will not try to execute that ddl file. It really looks like you manually modified the database structure at some point. |
As you see there are 2 users with this issue Ange7 and me. I did no manual modifications to the database structure before this issue occurred. |
No manual modifications too.... |
Oops, I though I'm talking with one person. Anyway, I downloaded 1.3.0 package and I see:
in SQL/mysql.initial.sql. So, now tell me how did you end up with "2016100900"? |
Ahaha i don't know, maybe in previous version INSERT INTO with 2016100900 value was executed and 1.3 upgrade fail to execute "INSERT INTO system (name, value) VALUES ('roundcube-version', '2016112200');" ? |
That's possible, but not a common case. Actually, as I know, no one had such an issue, and we'd know for now. And why didn't you notice then? Strange and rare so why bother. You have your fix, right? |
Nice reaction. thank you @ThASattler |
Our system was updated from 1.2.5 to 1.3.0 (and afterwards to 1.3.1 and 1.3.3). In version 1.3.1 there are two SQL-Scripts which are to be executed: During update to 1.3.0 script 2016100900.sql was executed and the value of 'roundcube-version' in system TABLE was updated to '2016100900'. When executing the next update from 1.3.0 to 1.3.1 the update process tried to execute 2016112200.sql because value of 'roundcube-version' was less than '2016112200'. But now the first line command to ADD COLUMN 'id' in 'dictionary' TABLE failed too. So table 'dictionary' was altered during last update but the tables 'cache' and 'cache_shared' were not. Both tables contained still the COLUMN You have to apply 2016112200.sql to your database and to update the value of 'roundcube-version' in 'system' TABLE to '2016112200'. |
I had the same issue. Originally installed 1.2.0 and upgraded to 1.3.0, then 1.3.3, but never had an issue until the 1.3.0 to 1.3.3 upgrade. Thank you for the fix. |
I'm commenting here because I had exactly the same problem. I was upgrading from 1.3 to 1.3.3. (I have a long history of upgrades, and not always with every single point release.) My version was listed as 2016100900, so I updated it manually. I then manually deleted the existing column "id" from table "dictionary," and, finally, applied 20161122200.sql again. I should add that I've never had a permissions issue (nor did I here), and I've never had to manually edit the Roundcube database before. |
I'll add myself to the list. I get this error with every 1.3x version. Now on 1.3.4. Can someone outline the exact steps to fix this? |
I have the same problem too upgrading from 1.2 to 1.3.4. Alexcpl is not being very helpful here. Does someone have an actual fix? iRedmail users are seeing this as they upgrade from old installs. |
I did a upgrade from 1.3.0 to 1.3.4 - same error for me. |
The last Update 2016112200.sql makes the problem.
DROP TABLE CREATE TABLE CREATE TABLE
|
Got same problem while updating from 1.3.8 to 1.4.0. Had to manually execute all SQL scripts. |
I had a similar issue and fixed it like this: |
Hello,
Today i try to upgrade my roundcube installation from 1.3.0 to 1.3.3 but i have one error at end :
Error 500 : Error in DDL upgrade 2016112200 [1060] Duplicate column name 'id'
In my dictionary table i already have "id" column, cache & cache_shared tables already exists too
Thank you for your help
The text was updated successfully, but these errors were encountered: