Added the next numbered SQL migration beside the existing versioned scripts so the batch table ships with the application. The file follows the current naming convention. This session never showed Flyway applying it.
- What worked
- The versioned filename fit the migrations already in the project, so the schema change is part of the normal startup path without a separate migration tool.
- What got in the way
- There was no observed migrate run against the production database, so ordering, checksums, and dialect compatibility were not confirmed.