Skip to content
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

Flyway uses schema_version table even if I specify the table to be flyway_schema_history #2148

Closed
swanke00 opened this issue Sep 25, 2018 · 1 comment

Comments

@swanke00
Copy link

@swanke00 swanke00 commented Sep 25, 2018

Duplicate of #1859

Originally posted by @axelfontaine in #1860 (comment)

The determineTable(Table table) method of JdbcTableSchemaHistory should FIRST check if the new default table (flyway_schema_history) exists before trying to fallback. Flyway should only fallback if the specified table name is not found.
For our app we have both a flyway version 3 and 4 compatible table present because our db is shared by our old and new release of software for zero downtime upgrades. This worked fine with flyway versions 3 and 4. Now we are upgrading to Spring Boot 2.0 which includes Flyway 5 the app won't start because flyway 5 is falling back to the schema_version table which is flyway 3 compatible.

@axelfontaine axelfontaine added this to the Flyway 5.2.0 milestone Sep 26, 2018
axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Sep 26, 2018
@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented Sep 26, 2018

This is quite an unusual scenario, but you are right that a check is missing there. Done. It has now been added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants