goto will continuously apply/rollback given migration

[awfm9]

When using the goto v syntax, each time there will be an action, either applying or rolling back the migration version in question. There should be clearly defined semantics (the version should probably be defined as the state after applying the up part of the migration) and issuing the same command twice should not change anything.

[mattes]

Is this version 1 or 3?

[awfm9]

It's version 1. Why did you go from version 1 to 3 by the way?

[mattes]

Can you check out version 3 and see if it works for you?

There was a version 2 internally used here. It was never released. Looking back that was a mistake, since it created so much confusion.