Flyway previous migration changed
flyway
Solution
Set `flyway.validateOnMigrate` to `true` and you should be good to go.
Problem
Here's my workflow: ``` Setup tables, constraints etc. in V1__CreateSchema.sql (checksum = c3a82bcf43b3c78a5ca4ebd25ca06005) ``` Run flyway migration --> database gets created. Then I realize that the schema needs to be updated: ``` Update sql statements in V1__CreateSchema.sql (checksum = 7e1aeb51d4e91b504cd920ec7af17092) ``` Run flyway migration --> flyway ignores the fact that a previously run migration's signature has changed. ``` [INFO] --- flyway-maven-plugin:2.3:migrate (default-cli) @ zeus --- [INFO] Current version of schema `mydb`: 1 [INFO] Schema `mydb` is up to date. No migration necessary. ``` Is this a supported workflow? I would expect flyway to fail stating that a fork has been made in the past migration path.