You should add flyway-mysql dependency. Maven : <dependency> <groupId>org.flywaydb</groupId> <artifactId>flyway-mysql</artifactId> </dependency> Gradel: dependencies { compile “org.flywaydb:flyway-mysql” } More information here.
I had the same problem with PostgreSQL 9.2, and used the following class to solve the problem. Be aware though that all the custom properties you might set in the Spring Boot properties will be ignored, since that replaces the whole Flyway autoconfiguration by your own. So you might have to add some additional code … Read more
For future visitors, this is a solution for DB specific sql, but applies to data loading too. https://flywaydb.org/documentation/faq#db-specific-sql You can set the flyway.locations=sql/common,sql/data property, and this can be set to different values with spring profiles(dev/test/prod), omitting the sql/data scripts on production.
The default for flyway.table has been changed from schema_version to flyway_schema_history. And they have also provided automatic fallback to old default with a warning to avoid breaking existing installations using the old default. It means from flyway 5, If you do not specify flyway.table property inside your configuration file, then flyway will look for the … Read more
“FlywayException: Detected failed migration to version 1.0” it means that you ran migrate before and it failed at 1.0 for some reason. You need to identify why the previous migration failed at 1.0 and solve it if you have already not done so. Once solved you need to run flyway repair to tell flyway that … Read more
I had the same issue. I wanted my schema to be created by hibernate because of it’s database independence. I already went through the trouble of figuring out a nice schema for my application in my jpa classes, I don’t like repeating myself. But I want some data initialization to be done in a versioned … Read more
Declaring your own DataSource will already have implicity disabled Spring Boot’s auto-configuration of a data source. In other words this won’t be having any effect: @EnableAutoConfiguration(exclude = {DataSourceAutoConfiguration.class}) I think the problem lies in the fact that you aren’t binding Hikari-specific configuration to your MySQL DataSource. You need to do something like this: @Bean @Primary … Read more
The first rule is don’t. The second one is do it very carefully and use Flyway.repair() to realign the checksums in the DB with the ones on disk.
You can use the flyway.locations property. In test in would look like this: flyway.locations=sql/common,sql/derby and in prod: flyway.locations=sql/common,sql/oracle You could then have the common statements (V1__Create_table.sql) in common and different copies of the DB-specific statements (V2__Alter_table.sql) in the db-specific locations. An even better solution, in my opinion, is to have the same DB in prod … Read more
A small correction, before I answer question. The assumption Liquibase seems to have everything Flyway has isn’t correct. Flyway shines when it comes to parsing SQL. You can use unmodified SQL files generated by your native tools containing all kinds of complexity like PL/SQL packages and procedures, MySQL delimiter changes, T-SQL, PostgreSQL procedures, … With … Read more