3 ms·
I don't use an ORM, because they're not a good fit for my project (also, for the reasons in the article). But I do have a pain point around migrations - I have
by marcus_holmes 7y ago
I don't use an ORM, because they're not a good fit for my project (also, for the reasons in the article).
But I do have a pain point around migrations - I have to either painfully hand-write migrations for the deploy code to deal with, or hand-alter the production database to make it fit the new schema. Neither of which are good solutions.
Totally stoked to see the automigrate tool. It completely fits my pain point. Ideally I can have a line in my make file that compares the current schema with the last-known production schema and automagically generates a migration for it.
I'll have a play with this, and contribute if I can.