How can we help you today? How can we help you today?
Dan Calver
Hi Azmat, On Postgres, when a migration fails partway through, the database can undo everything it did — including telling Flyway "this one failed." So Flyway never even writes a record of the attempt. Next time you run migrate, it just looks like the failed attempt never happened. Oracle can't offer that guarantee across the board — some things Oracle does (schema changes, in particular) can't be undone once started, no matter what. Because Flyway has to treat Oracle consistently, it plays it safe for every Oracle migration: it always writes down "this one failed" before it can know whether the failure was something undoable (like your data update) or something it couldn't have undone anyway. It can't tell the difference in advance, so it treats a DML-only failure the same as a DDL failure. That's why you end up with a leftover "failed" record even though your actual data change rolled back cleanly — Oracle rolled back the data, but Flyway still keeps the paper trail of the failed attempt, and it won't proceed until you clear that paper trail. Performing ‘flyway repair’ is the officially supported mechanism to address this issue, to make life easier you could add this as a automatic step in your deployment pipeline that runs before migrate.   / comments Official comment
Hi Azmat,On Postgres, when a migration fails partway through, the database can undo everything it did — including telling Flyway "this one failed." So Flyway never even writes a record of the attem...
0 votes
Hi Micro, There are no changes around this area when it comes to our products unfortunately, and if you wish to view history it will need to be done via the repo directly / comments
Hi Micro,There are no changes around this area when it comes to our products unfortunately, and if you wish to view history it will need to be done via the repo directly
0 votes
Hi all, This is unfortunately an issue due to the changes in SSMS 21 & 22s with it's order of operations. To workaround this, if you open SSMS, open SQL Source Control tab, then close and re-open SSMS the icons should now display correctly / comments
Hi all,This is unfortunately an issue due to the changes in SSMS 21 & 22s with it's order of operations.To workaround this, if you open SSMS, open SQL Source Control tab, then close and re-open SSM...
0 votes