db-migration
Writes a Flyway database migration for this project following the team's rules for naming, editing and renaming, so migrations from different developers don't collide and deployed databases stay valid
SKILL.mdplugins/springboot-architecture/skills/spring-boot-team-harness/assets/project-skills/db-migration/SKILL.md
GitHubWrite a database migration
Migrations live in src/main/resources/db/migration.
- Follow the naming the folder already uses. In a folder with no migrations yet, use
V<yyyyMMddHHmm>__<what_it_does>.sqlin UTC: unlikeV7,V8, timestamps don't collide when two developers add a migration on different branches. With numbered names, take the next number after the highest one on the main branch, and renumber yours if someone merges first. - Never edit a migration that is on the main branch. It may already have run on a shared database, and Flyway fails validation when the checksum changes. Write a new migration instead.
- Make destructive changes in two releases. To rename or drop a column, first add the new column and write to both, and drop the old one in a later migration once no running version reads it.
- Keep each migration to one purpose. Put data fixes in their own file, and make them safe to run on a database where the fix is already done.
- Don't let Hibernate create the schema:
spring.jpa.hibernate.ddl-autostaysvalidateornone. - Run
./mvnw verify. If the project has Testcontainers integration tests, they apply every migration to a real database; if it has none, say that the migration is untested.