Flyway cannot create schema table on Galera cluster (MariaDB) #1293
Milestone
Comments
erindru
pushed a commit
to erindru/flyway
that referenced
this issue
Apr 26, 2016
…o that Flyway can work on servers with 'innodb_force_primary_key' enabled. Fixes flyway#1293
axelfontaine
added a commit
to flyway/flywaydb.org
that referenced
this issue
May 5, 2016
Thanks Erin! PR merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Flyway are you using?
4.0
What database are you using (type & version)?
MariaDB 10.1.13. Note: this issue is caused by setting
innodb_force_primary_key=1
which is required for the Galera cluster to work properly. You dont need to set up a Galera cluster to reproduce this issue, you can do it by setting that property on a normal MariaDB instance.What operating system are you using?
Mac OSX and Linux
What did you do?
Ran Flyway.migrate() and observed the following error:
What did you expect to see?
The
schema_version
table created successfullyWhat did you see instead?
A
This table type requires a primary key
error returned from the database serverSince you use DB-specific SQL for each database, the following script can be updated to create a primary key at the same time as the table instead of directly afterwards: https://github.com/flyway/flyway/blob/master/flyway-core/src/main/resources/org/flywaydb/core/internal/dbsupport/mysql/createMetaDataTable.sql
I will submit a pull request for this.
The text was updated successfully, but these errors were encountered: