Flyway out of order and idempotent migrations -


we in situation similar this blog post 2013.

because there 1 project used many developers, we'd implement outoforder functionality flyway. above mentioned post makes claim sql have written using idempotent commands, such "if not exists" etc.

when attempting reproduce issue post, noticed did not matter outoforder apply earlier sql file without attempting applied migrations.

was fixed since original post? there i'm missing?

outoforder applies unapplied versions made after baseline of database.

if database wasn't baselined start, applies versions have not been applied, flyway doesn't apply have been applied.

i believe article referring manually reapplying file.


Comments