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

When migrations have been applied by enabling out-of-order Flyway displays the wrong current version #1457

Closed
rousej opened this issue Oct 26, 2016 · 1 comment
Labels
Milestone

Comments

@rousej
Copy link

@rousej rousej commented Oct 26, 2016

What version of Flyway are you using?

4.03

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)

Java API

What database are you using (type & version)?

Oracle 11g, MS Sql Server 2012, 2014

What operating system are you using?

Windows 7

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
I applied migrations in-order beginning with a baseline version of 12.3.2.0.0.0.990 and ending with version 17.1.0.0.0.0.990. I then applied migration version 12.4.0.0.0.0.130 by enabling out-of-order. All migrations were successfully applied. The next time I ran flyway migrate I received the following output:

Flyway 4.0.3 by Boxfuse
Database: JDBC Driver; (Microsoft SQL Server 12.0)
Successfully validated 104 migrations (execution time 00:00.211s)
SQLServer does not support setting the schema for the current session. Default schema NOT changed to dbo
Current version of schema [dbo]: 12.4.0.0.0.0.130
outOfOrder mode is active. Migration of schema [dbo] may not be reproducible.
Schema [dbo] is up to date. No migration necessary.

What did you expect to see?

I expected to see the highest successfully applied migration version displayed as the Current version.

What did you see instead?

The Current version was displayed as 12.4.0.0.0.0.130, which was the last migration applied chronologically, but not the highest migration version applied.

@axelfontaine axelfontaine added this to the Flyway 4.1 milestone Oct 28, 2016
axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Jan 31, 2017
@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented Jan 31, 2017

Good catch! Thanks for reporting!

pradheeps pushed a commit to pradheeps/flyway that referenced this issue Mar 7, 2017
…f-order Flyway displays the wrong current version
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
You can’t perform that action at this time.