Unable to discard a migration after undoing it

[axelfontaine]

Customer report

I started with this:

I then rolled back V4, and got this:

At this point you say I can ‘discard it altogether’. So I tried deleting the files, which led to this (note the missing status):

Attempting a migrate at this stage leads to this:

So I’m not clear on how I can discard an undone migration?

At this point I tried the second scenario of amending the V4 file. So I renamed the file from V4__Another_person.sql to V4__Another_person_next_try.sql. If I delete the corresponding U4__Another_person.sql, I get this:

And if I leave the U4__Another_person.sql in place I get this:

But either way, the result of attempting a migrate is this:

So finally I tried leaving the existing versions of V4__Another_person.sql and U4__Another_person.sql in place and adding V4__Another_person_next_try.sql as well. This led to the following:

So I’m not clear on how I can either re-implement a previous version or completely abandon it…

Note that the only thing that did work was to edit the contents of the undone file without altering the name and then running migrate – but this doesn’t help in the case where I want to undo a change and completely discard it, or replace it with something different (so that the description from the file is no longer applicable).

[axelfontaine]

Fixed.