Rollback support

It would be great to have a rollback feature so that the schema can be rolled back to a specific migration. The functionality could be similar to EF migrations rollback.

Here’s the intended functionality:

Assume there are 4 migration scripts 1.1, 1.2, 1.3, 1.4

When migrate command is executed with a specific version e.g. 1.3 all migrations greater than that (1.4) will be rolled back by executing the corresponding rollback script. This means, in addition to the migrations directory, users need to provide a rollback directory with the rollback scripts (Similar to Up() and Down() methods in EF).

This functionality will be similar to EF Update-Database command.

[IndikaUdagedara]

Thanks @lecaillon

The use case is actually to get the db back to a stable state after a faulty migration. E.g. migration 1.4 broke something (although got successfully applied) so need to revert back to 1.3. I guess this could be achieved by rolling forward i.e. deploying a new 1.5 script to revert the changes in 1.4 but having a rollback feature would make it convenient for CI/CD. The steps would be

• Run migration x
• Run tests
• If tests fail revert x, otherwise mark the deployment as success

[IndikaUdagedara]

We found DB migration rollbacks is problematic (although it sounds a nice feature). We ended up with

• ensuring database changes are always backward compatible
• rolling forward i.e. instead of rolling back a previous one, create a new migration with