-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
DB migrations fail in Docker with MariaDB 10.4.31 #1212
Comments
When running database migrations with the latest 10.4.31, they fail as shown in issue steve-community#1212. Pinning the point release of MariaDB to the latest known-good version maneuvers around this issue.
When running database migrations with the latest 10.4.31, they fail as shown in issue steve-community#1212. Pinning the point release of MariaDB to the latest known-good version maneuvers around this issue.
When running database migrations with the latest 10.4.31, they fail as shown in issue steve-community#1212. Pinning the point release of MariaDB to the latest known-good version maneuvers around this issue. Co-authored-by: Sevket Gökay <sevketgokay@gmail.com>
I also ran into the 0.7.7 and 0.8.6 migration failures using the released version 3.6.0 of steve. You may want to re-release soon! I was able to successfully finish the migrations with these files (renamed to .txt to upload to github): But I may still have mistakes as I then ran into:
I am running this via Docker. |
If I download the latest from git, I also get the java.lang.IllegalStateException. I'll open a seperate ticket for that. |
Checklist
Specifications
Expected Behavior
Starting up application and database containers succeeds.
Actual Behavior
Starting up the application container fails at running database migrations.
Steps to Reproduce the Problem
Stop and remove eventually running instances and volumes
Clone repository
Running database fails and there are multiple types of issues (so far)
Presence of foreign keys in an early stage of the migration
which I could circumvent by reordering dropping and creating keys in
V0_7_7__update.sql
An issue with locking the table
schema_version
which I could circumvent by locking the table
schema_version
for writing inV0_8_6__update.sql
as well.set FOREIGN_KEY_CHECKS = 0
seems to be ignoredwhere I gave up fixing the issues I've seen so far.
Additional context
The text was updated successfully, but these errors were encountered: