-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark migration as already executed #190
Comments
First, did you manage to "fix" the Evolve metadata table ? @Zarun1 Then, it is an interessant idea just need to think about the easiest way to implement it in Evolve. |
I did. First I manually added rows to the metadata table so that it looked like I used Evolve to run the migrations. Then I used "evolve repair" command to fix the checksums. The end result worked well. |
What about an option called
|
Available since Evolve 3.0.0-alpha6 |
I'm working on a database project where we use Evolve to handle migrations. A team member carelessly made changes to the production database without using Evolve. After realizing the situation, we added migration scripts matching those changes to version control. But now we have a production database where those changes have already been made, without Evolve knowing about it. The changes added new table columns that now have data in them, so we can't simply reverse the changes and then make them again using Evolve.
Would it be possible to add a feature to Evolve that allows marking migration scripts as already executed, without actually executing them? I believe it would only need to add rows to the database version history table that show the migrations have been run.
This is a feature supported by Flyway Teams (skipExecutingMigrations option). They've implemented this as part of the migrate command.
The text was updated successfully, but these errors were encountered: