Better database migrations handling

[YuukanOO]

At the moment, it feels like migrations are not applied in a transaction and as such could make the database inconsistent and unusable if a migration has failed. This should be improved.

To make sure migrations are applied in a specific order, it will be better to accept an array of migrations dir instead of an unordered map:

seelf/pkg/storage/sqlite/database.go

Line 67 in 1eba5d9

func (db *database) Migrate(migrations MigrationsDir) error {

[YuukanOO]

Looks like migrations are applied in a transaction but if it fails, go-migrate will still set the version to the failed one with the dirty flag set to 1 so a user intervention is necessary.

I'm not sure about this but migrations should not fail in a release environment, so maybe that's pointless after all. Migrations could fail when developping but that's all.

[YuukanOO]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

• v1.1.0
• GitHub release

Your semantic-release bot 📦🚀