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

Introduce option to fail migrate if has a version that is newer than the latest available migration #989

timbuethe opened this issue Apr 10, 2015 · 6 comments


Copy link

@timbuethe timbuethe commented Apr 10, 2015

If the schema contains a migration that is newer than the latest available, migrate logs a warning but doesn't fail. For example:

Schema xxx has a version (1.1.1) that is newer than the latest available migration (1.0.1) !

I suggest to introduce an option to fail migration if this is detected to prevent running an older version of software on a newer database schema.

This is related to, which would lead to failing if a migration isn't found:

Related stackoverflow question:

Copy link

@blootac blootac commented Jul 16, 2015


4 similar comments
Copy link

@rapguit rapguit commented Jul 16, 2015


Copy link

@PeeZu PeeZu commented Jul 17, 2015


Copy link

@syedtariqislam syedtariqislam commented Jul 29, 2015


Copy link

@diwakartimilsina diwakartimilsina commented Aug 10, 2015


@axelfontaine axelfontaine added this to the Flyway 4.0 milestone Nov 2, 2015
Copy link

@axelfontaine axelfontaine commented Feb 3, 2016

Added new ignoreFutureMigrations flag (default = true)

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

Successfully merging a pull request may close this issue.

None yet
7 participants