Crash and idempotent migrations
We are in a situation similar to this blog post from 2013.
Since there is one project that will be used by many developers, we would like to implement the OutOfOrder functionality from Flyway . However, the above post states that SQL should be written using idempotent commands such as "IF NOT EXISTING" etc.
When trying to reproduce the issue from the post, we noticed that it didn't matter as OutOfOrder applied the previous SQL file without trying to apply migrations that were already applied.
Has this been fixed from the original post? Is there something I am missing?
source to share
OutOfOrder only applies non-applicable versions that are built past the database baseline.
If the database has not been configured to run, then it applies all versions that have not been applied, Flyway does not apply those that have already been applied.
I believe the article referred to manual file reuse.
source to share