Comments
Sort by recent activity
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...
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 ...