Migration failed: migration 20221113170740 failed #1573

New Issue

zhzy0077 · 2023-07-10T06:12:18Z

zhzy0077 commented

2023-07-10 06:12:18 +00:00

Description

I saw below error in Docker logs:

2023-07-10T06:06:42.439717424Z: CRITICAL	▶ migration/Migrate 051 Migration failed: migration 20221113170740 failed: Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'COLUMN `list_id` TO `project_id`' at line 1

info: creating the new user vikunja with 1000:1000

usermod: no changes

2023/07/10 06:07:42 No config file found, using default or config from environment variables.

Rollback to vikunja/api:0.20.4 helps

Vikunja Frontend Version

vikunja/frontend:latest@sha256:07b70a5c82a6fd8913f913a7c960650b684715b919a565cde85fea5214c42cec

Vikunja API Version

vikunja/api:latest@sha256:d622ec11f1116ba04d46d42a425364fe732befd4cb9ffcdd3324801fcbc07c57

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description I saw below error in Docker logs: ``` 2023-07-10T06:06:42.439717424Z: CRITICAL ▶ migration/Migrate 051 Migration failed: migration 20221113170740 failed: Error 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'COLUMN `list_id` TO `project_id`' at line 1 info: creating the new user vikunja with 1000:1000 usermod: no changes 2023/07/10 06:07:42 No config file found, using default or config from environment variables. ``` Rollback to vikunja/api:0.20.4 helps ### Vikunja Frontend Version vikunja/frontend:latest@sha256:07b70a5c82a6fd8913f913a7c960650b684715b919a565cde85fea5214c42cec ### Vikunja API Version vikunja/api:latest@sha256:d622ec11f1116ba04d46d42a425364fe732befd4cb9ffcdd3324801fcbc07c57 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_

zhzy0077 added the

kind/bug

label 2023-07-10 06:12:18 +00:00

konrad commented

2023-07-10 07:54:06 +00:00

Which database are you using?

konrad commented

2023-07-10 07:54:25 +00:00

Are you on a fresh install or an upgrade?

zhzy0077 commented

2023-07-10 13:06:38 +00:00

MYSQL 5.7

Upgrade from 0.20.4

MYSQL 5.7 Upgrade from 0.20.4

konrad commented

2023-07-10 13:59:23 +00:00

Looks like mysql changed the rename sql statement between 5.7 and 8.0. Mariadb and other variants seem to use the same statements as 8.0.

Unfortunately, I don't see a path where we can support 5.7 without much of a hassle. While the change itself is one if statement, there would be added complexity to detect if a database uses 5.7 or 8.0. At the same time, 5.7 will reach end of life later this year at which point we'll stop supporting it for usage with Vikunja anyway. And we'll start using features of 8.0 with the next release.

What's preventing you from upgrading to 8.0?

Looks like mysql changed the rename sql statement between 5.7 and 8.0. Mariadb and other variants seem to use the same statements as 8.0. Unfortunately, I don't see a path where we can support 5.7 without much of a hassle. While the change itself is one if statement, there would be added complexity to detect if a database uses 5.7 or 8.0. At the same time, 5.7 [will reach end of life later this year](https://endoflife.software/applications/databases/mysql) at which point we'll stop supporting it for usage with Vikunja anyway. And we'll start using features of 8.0 with the next release. What's preventing you from upgrading to 8.0?

konrad closed this issue

2023-07-10 13:59:23 +00:00

Sign in to join this conversation.