Undo followed by repair leads to corrupted schema history #2219
Labels
Milestone
Comments
axelfontaine
added a commit
to flyway/flywaydb.org
that referenced
this issue
Nov 30, 2018
axelfontaine
added a commit
that referenced
this issue
Nov 30, 2018
Thanks for the detailed report and the investigation. This was very helpful in identifying the issue! Fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which version and edition of Flyway are you using?
5.2.3 pro
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command-line
Which database are you using (type & version)?
H2 1.4.197
Which operating system are you using?
Windows 7 Pro SP1
What did you do?
Settings:
flyway.outOfOrder=true
Starting with an empty history table and only 2 sql files:
V1.1__hello.sql
U1.1__hello.sql
flyway migrate
flyway undo
I changed the content of V1.1__hello.sql
flyway repair
flyway migrate
flyway undo (3 times)
What did you expect to see?
No corrupted table
What did you see instead?
The text was updated successfully, but these errors were encountered: