Hacker News Reader

You eyeball the statements? Thats 100% unreliable, I'll just wait for your sugar to go down while you do that.

Migration that is not automatic is not an option.

Yes, I eyeball the migration code. You could call it code review, whatever. There is no way I am running migration code automatically. In fact I am not sure what you mean by "automatically"? As in a non-human triggers the migration? But do you review the code?

First of all, migrations do not happen in my case that often that I need them to run unattended/automatically.

Second, I don't trust any migration system to spit out flawless code. Maybe I have trust issues.

If migrations are rare, you are supporting old system.

Migrations are there every few days on my projects. Non automatic migration is IMO not a migration but database intervention, just as non-automatic tests are not really tests.

This is the first I'd heard of migra but I can definitely imagine a solution involving piping the schema-diff between two databases (e.g. uat and local-dev) into some file that eventually gets applied in prod.

Seems easier than manually creating diffs which is what existing automatated migration tools seem to want you to do.

I love that it's just the diff. Makes it easier to integrate into cloud-native pipelines.

Reply on news.ycombinator.com