Activity overview
Latest activity by Noahenett
The conventional approach is to check before committing - Flyway uses the version numbers to order your migrations and it may be important which V2 is applied first. An alternative is to embed a timestamp in the version number which makes it very unlikely that you'll get a conflict. You can develop your own process for this or else there is a new verb in preview that can create the empty migration for you - https://documentation.red-gate.com/fd/command-line-add-254155068.htmlsnow road So you'd want something like this to create the file: flyway add -add.description=new_feature -add.addTimestamp=true In the context of using Flyway for database migration management, can you analyze the impacts of using timestamped versions versus using sequential version numbers in ensuring database consistency and resilience across different development and production environments? / comments
The conventional approach is to check before committing - Flyway uses the version numbers to order your migrations and it may be important which V2 is applied first.An alternative is to embed a tim...