I never experienced anything like this in Rails or Phoenix (Ecto) land. The only time I had problems with database migrations were in javascript with Prisma. B

I never experienced anything like this in Rails or Phoenix (Ecto) land. The only time I had problems with database migrations were in javascript with Prisma. But that was because we had a local dev dataset, and the CEO had gone into past migration files and edited them manually. Prisma exploded every time and it was a pain to fix. It sounds like your pains are also coming from people manually editing past migration files and committing them. Don't do that!