Activity overview
Latest activity by 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...
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
Hi, I can confirm you're correct, execution_time is stored in milliseconds. / comments
Official comment
Hi,I can confirm you're correct, execution_time is stored in milliseconds.
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...
Hi Benjamin, In this case, scenario B works because Snowflake will only consume the private_key_file when it's part of the JDBC URL. Does the private_key_file need to be variable? I would try something like the following ## Environment: Dev
[environments.dev]
url = """jdbc:snowflake://XXXXXX.snowflakecomputing.com?{$private_key_file_variable}\ Then you can set up your private_key_file as an environmental variable. / comments
Official comment
Hi Benjamin,In this case, scenario B works because Snowflake will only consume the private_key_file when it's part of the JDBC URL. Does the private_key_file need to be variable?I would try somethi...
Sign commits with an SSH key
If Git is configured to use commit signing with an SSH key, you won’t be able to commit through Flyway Desktop’s Version Control tab, the icon will simply continue spinning.This happens because Fly...
Hi Vlad, Unfortunately, Flyway itself cannot change how PostgreSQL handles DDL locking. The ALTER TABLE ADD COLUMN command in Postgres requires an ACCESS EXCLUSIVE lock, which blocks read and writes to the table until the statement completes. This is a PostgreSQL behavior, not something Flyway can override. To change this, you could change the DDL statements, but that would require manual change. You're correct in your assumption, that property only affects its own flyway_schema_history table. / comments
Official comment
Hi Vlad,Unfortunately, Flyway itself cannot change how PostgreSQL handles DDL locking.The ALTER TABLE ADD COLUMN command in Postgres requires an ACCESS EXCLUSIVE lock, which blocks read and writes ...
Hi Max, This is default behaviour for a SQL Change Automation project, to change this for your existing project, please edit the .sqlproj file in notepad, then if you paste this into the file it will allow you to script partition schemes/functions. <SyncOptionIgnoreDataspaces>False</SyncOptionIgnoreDataspaces> Example: [image] / comments
Official comment
Hi Max,This is default behaviour for a SQL Change Automation project, to change this for your existing project, please edit the .sqlproj file in notepad, then if you paste this into the file it wil...
Hi Bo Ngoh Sorry, to hear you're experiencing this issue! I just tested this scenario myself without issue, so I'm wondering do you know what version of SQL Change Automation you're using? It could also be the case of different comparison options causing trouble. I'm happy to reach out directly via a support ticket to troubleshoot further if that works for you! / comments
Hi Bo Ngoh Sorry, to hear you're experiencing this issue!I just tested this scenario myself without issue, so I'm wondering do you know what version of SQL Change Automation you're using?It could a...
Hi Steven Vallarian Could you please post the request here: https://redgate.uservoice.com/forums/141379-sql-compare / comments
Hi Steven Vallarian Could you please post the request here: https://redgate.uservoice.com/forums/141379-sql-compare