Use a different tool for DB migrations

[rkatic]

As @iblazevic brought to our attention, migratio seems to not be well maintained (last commit done in 2017), neither it gained a significant user-base.

@PetarIvancevic pointed to an interesting alternative: https://github.com/thomwright/postgres-migrations

[jglasovic]

As @iblazevic brought to our attention, migratio seems to not be well maintained (last commit done in 2017), neither it gained a significant user-base.

@jglasovic pointed to an interesting alternative: https://github.com/thomwright/postgres-migrations

Not me, @PetarIvancevic pointed to this alternative :)

[kula124p]

No down migration is a bold decision.
Down migration can be cumbersome (when deleting stuff definitely) but it's rather useful nonetheless.
This "Idemo dalje!" methodology is an interesting one... Doesn't work very well in practice in my experience :^)

[rkatic]

@jglasovic selected you by mistake.. going to fix the description.

@n00ne1mportant would be interested to hear in what cases you are finding down-migrations more useful than new forward ones, since in my experience I didn't find those useful for few reasons:

• often not everything can be reversed with down migrations
• usually are hard/cumbersome to test
• therefore not reliable as new forward ones
• almost never needed to "reverse" a migration (why then to even bother to write every time unstable/incomplete down migrations)

[kula124p]

@rkatic
Since I never given it too much thought I did the responsible thing and googled it. Deeply. The way I've seen down migration is like a big red button you hit when you screw up the DB. You can revert API code easily but not the DB which means if migration fails on production you are stuck between a rock and a hard place (screwed).
Without down migration you can't bring back working previous version while finding the bug so it's creates pressure and downtime.
But basically everything you said is correct. They are cumbersome at best.

In some (mostly virtualizied) environments they are impossible anyway so I'm guessing moving forward without them makes sense when I think about it 👍

[rkatic]

postgres-migration is being added with #36