Spring Flyway Support: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
Flyway database migration is automatically triggered on startup if "org.flywaydb:flyway-core" dependency is present in the application's classpath. | Flyway database migration is automatically triggered on startup if "org.flywaydb:flyway-core" dependency is present in the application's classpath. | ||
The migration script naming convention is V<''version''>_<''name''>.sql where: | |||
* <''version''> is an underscore separated version, such as "1" or "1_2". | |||
The migration script default location is "classpath:db/migration[/{vendor}]", but it can be overridden with the "spring.flyway.locations" property, which should contain a comma-separated list of one or more classpath: or filesystem: locations. | |||
spring.flyway.locations=classpath:db/migration,filesystem:/opt/migration | |||
The {vendor} placeholder is set according to the type of database. | |||
=Organizatorium= | =Organizatorium= | ||
Revision as of 21:14, 4 December 2018
Internal
Overview
TODO
- Understand how main/resource/db/migration/V1.0_init.sql drives schema creation with Spring Data JPA.
Database Migration on Startup
Flyway database migration is automatically triggered on startup if "org.flywaydb:flyway-core" dependency is present in the application's classpath.
The migration script naming convention is V<version>_<name>.sql where:
- <version> is an underscore separated version, such as "1" or "1_2".
The migration script default location is "classpath:db/migration[/{vendor}]", but it can be overridden with the "spring.flyway.locations" property, which should contain a comma-separated list of one or more classpath: or filesystem: locations.
spring.flyway.locations=classpath:db/migration,filesystem:/opt/migration
The {vendor} placeholder is set according to the type of database.
Organizatorium
- Disable flyway support: