Hi developers,
I used the new Flyway Enterprise credentials, but I am still facing one issue.
Below is my script:
(used it in spring boot gradle)
I added the new credentials to my flyway.conf file. When I ran the migration, it threw an SQL syntax error, which is fine. However, the entire migration was marked as failed, but the first DROP COLUMN name statement was still executed, and the column was dropped from my table.
After fixing the syntax error in the second statement, I reran the migration, but it showed that there were failed migrations. I then used the repair command to clear the failed state and ran the migration again. This time, it threw an error saying, "No column/key found for the column 'name'" because the column had already been dropped.
It seems there’s no existence check happening here. I need a solution from your end for this issue. Additionally, I would like guidance on handling similar scenarios withADD COLUMNSCREATE TABLES and other migration operations.
Thanks.
Hi developers,
I used the new Flyway Enterprise credentials, but I am still facing one issue.
Below is my script:
(used it in spring boot gradle)
I added the new credentials to my
flyway.conffile. When I ran the migration, it threw an SQL syntax error, which is fine. However, the entire migration was marked as failed, but the firstDROP COLUMN namestatement was still executed, and the column was dropped from my table.After fixing the syntax error in the second statement, I reran the migration, but it showed that there were failed migrations. I then used the
repaircommand to clear the failed state and ran the migration again. This time, it threw an error saying, "No column/key found for the column 'name'" because the column had already been dropped.It seems there’s no existence check happening here. I need a solution from your end for this issue. Additionally, I would like guidance on handling similar scenarios with
ADD COLUMNSCREATE TABLESand other migration operations.Thanks.