django-migration-linter

I’m a bit surprised to hear that is the state of migrations in Rails. Being a Django developer I’m used to having most of the points you mention covered for a really long time already. It’s timeless by looking at a captured schema, that doesn’t change with later code changes. Which means you can’t import / use methods of models and have to copy those over. So a different way than using the vcs for this, but still. Not sure I’d name the second point “scalable”, but you can easily do data migrations as well. It is really easy to use! And you can certainly write tests for it, although it isn’t included in the framework [0]. But you can do that with just SQL too [1]. What I find much harder with (somewhat) larger dbs, is is a) determining whether it will lock up too much and b) whether it backwards compatible (so that you can roll back). Whic

A tool I've used with Django in the past is the one: https://github.com/3YOURMIND/django-migration-linter It helps with the problem that if you're running several application servers it's important to avoid migrations that are backwards incompatible - since if some of your application servers haven't yet updated to the latest code you could get errors when they try to run queries against the migrates database.