I'm just in the process of configuring and fully understanding flyway and I came into this situation:
However, once that I made the necessary changes to the corresponding script to work, flyway kept showing this message:
Current schema version: 1.0.4
com.googlecode.flyway.core.migration.MigrationException: Migration to version 1.0.4 failed! Please restore backups and roll back database and code!
Since I didn't want to restore a complete dump and apply every migration again, just to make an alter table script to work, what I finally did were some changes to the 'schema_version' table:
After this, the migration finally was applied and a success message shown, however I´m not quite sure if this is the right approach to deal kind of this situations. I'm no sure if its right to modify the 'schema_version' table by myself since i think it should only be modified by flyway itself.
So, after explaining what happened to me, my question would be:
Is there a way to 'retry' to apply a failed migration in flyway, without modifying the 'schema_version' table by myself?
Any command I'm not aware of to fulfill this task?
This is answered in the FAQ: http://flywaydb.org/documentation/faq.html#repair
The upcoming Flyway 2.0 will include the repair command. This code is already checked into SCM.
Note: This only deals with Flyway's metadata table. You are still responsible for cleaning up any other effects of a failed migration.
Update: Flyway 2.0 has now been released. You can grab it at http://flywaydb.org