Detected resolved migration not applied to database on flyway
Solution 1
The migration option outOfOrder
is your friend here. Set it to true to allow inserting those migrations after the fact.
On the command line, run:
flyway -outOfOrder=true migrate
Or if you use the Maven plugin:
mvn -Dflyway.outOfOrder=true flyway:migrate
Solution 2
I faced similar problem when switching from one git branch to another and tried to run
flyway:migrate
.
For example when I was on branch 'release_4.6.0' I didn't have migrations on my local machine from branch 'release_4.7.0' so
I received next error
FlywayException: Validate failed: Detected applied migration not resolved locally
.
The solution that worked for me is to set ignoreMissingMigrations
flyway option to true.
In maven it looks like
flyway:migrate -Dflyway.ignoreMissingMigrations=true
Maybe it's not an answer for this question, but it can be helpful for those who faced the same problem as me.
Here you can find more details: https://flywaydb.org/documentation/configuration/parameters/ignoreMissingMigrations
Solution 3
just add spring.flyway.ignore-missing-migrations=true
to your properties file if you are using spring-boot.
This will ignore previous migrations.
Solution 4
You can also put it in your application.properties
file if you want to apply the migrations when starting up the app:
spring.flyway.out-of-order=true
Joey Yi Zhao
Updated on July 09, 2021Comments
-
Joey Yi Zhao almost 3 years
We are using flyway to manage database schema version and we are facing a problem. Since we work as a team and use git as our source code management, there would be some cases that different people update database schema on their own local repo. If that happens, we will get
Detected resolved migration not applied to database: 2016.03.17.16.46"
The time "2016.03.17.16.46" was added by another person and I have already applied some timestamp later than that time. If that happens, we have to clean all database tables and create them again. We have tried to set false on
validateOnMigrate
and didflywayClean
, but nothing help. Is there another way to change that? -
JacobChan about 6 yearshow to do that in action?
-
Linda Z almost 6 years
flyway -outOfOrder=true migrate
-
Adriaan Koster almost 5 yearsNote that not all migrations can be executed out of order. For instance, creating table 'foo' and adding column 'bar' to table 'foo'.
-
Nikita Bosik over 4 years
-Dflyway.outOfOrder=true
-
Manish about 4 yearsWorked for me, but looks like there is some conceptual difference in how migration work in other frameworks and in flyway.