Mark migration as already executed

[Zarun1]

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.

[lecaillon]

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.

[Zarun1]

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.

[lecaillon]

What about an option called SkipNextMigrations used with the command migrate ? When run, Evolve would mark all next available migrations successful and stop.
This new option can be used with TargetVersion to only skip migrations until the targeted one (included).

• Example with the Evolve CLI to skip all migrations until version 8.9 included:

evolve migrate postgresql -c "Server=localhost;Databa..." -l "C:\db\..." --skip-next-migrations true --target-version 8_9

[lecaillon]

Available since Evolve 3.0.0-alpha6