Flyway doesn't execute repeatable migrations always, only if the checksum changes. This could sometimes be a problem, for example when dropping TimescaleDb hypertables that require to drop with `cascade`. It turns out that Flyway 6.3.0 introduced timestamp placeholders that could solve the issue: ```sql R__create_views.sql -- ${flyway:timestamp} create or replace view myview as ... ``` More info: - [sql - Flyway always execute repeatable migrations - Stack Overflow](https://stackoverflow.com/questions/63091283/flyway-always-execute-repeatable-migrations) - [Timestamps and Repeatable Migrations - Flyway](https://flywaydb.org/blog/flyway-timestampsandrepeatables) #flyway ![[Screenshot 2022-04-06T16.53.png]]