Conversation
Signed-off-by: Uroš Marolt <uros@marolt.me>
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
2 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
There was a problem hiding this comment.
Pull request overview
Enables Flyway “mixed mode” in migration scripts so migrations containing both transactional and non-transactional statements can run without failing.
Changes:
- Add
-mixed=trueto Flyway CLI invocation for the “product” migration image. - Add
-mixed=trueto Flyway CLI invocation for the “database” migration image.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| backend/src/product/flyway_migrate.sh | Enables Flyway mixed mode during product DB migrations. |
| backend/src/database/flyway_migrate.sh | Enables Flyway mixed mode during database DB migrations. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Note
Medium Risk
Changes database migration execution behavior by allowing mixed transactional/non-transactional statements, which can affect migration safety/ordering and rollback characteristics at deploy time.
Overview
Enables Flyway
-mixed=truein bothbackend/src/database/flyway_migrate.shandbackend/src/product/flyway_migrate.sh, allowing migrations that combine transactional and non-transactional statements to run successfully.Written by Cursor Bugbot for commit cd7d111. This will update automatically on new commits. Configure here.