Missing migrations handling. BMP-596

[Stepych]

resolves #73

[VojtechVitek]

You don't expect us to merge this change github.com/mc2soft/goose, do you? :)

Can you iron this PR out and provide a high-level overview of what is this PR supposed to solve? Thanks!

[Stepych]

This PR resolves #73. Ok, i will iron it to avoid "mc2soft" mentions)) But pls give me feedback, do you consider such issue?

[VojtechVitek]

So in the high-level, this would find all the missing migrations -- ie. all migrations that are available but were not applied in the DB, right?

You can

1. list them
2. apply them

[Stepych]

Yes, with new commands:

1. status-missing
2. up-missing

[VojtechVitek]

Now, do we need 1. at all? Can't goose status show these migrations as well by default?

Imho, 2. is explicit enough. I like it. It might even help people who insist on using Timestamp based migrations #63.

[Stepych]

status show all migrations (could be a lot of them!), including missing ("pending"). But the new status-missing shows only missing migrations.

[VojtechVitek]

I'd like someone from #63 to test this feature. I don't really have the same use case. Can you ping these guys, once you have the PR ready?

[VojtechVitek]

This is still not finished. We can't merge references to the github.com/mc2soft/goose fork.

[VojtechVitek]

@Stepych are you planning to finish this PR?

Or should we freeze it / close it? Thanks!

[VojtechVitek]

Closing due to inactivity

EDIT:
I've also closed the original issue, since I believe we don't want to apply any missing migrations.

We explicitly prefer to error out if there's any gap in the migrations. If goose skips those migrations right now, it's probably a bug and we should fix that and make it an error.

We don't want to apply any migrations that are out of the sequence number order.

There shouldn't be any "skipped" migration if you version your migrations properly. See https://github.com/pressly/goose#hybrid-versioning for further explanation.