4 ms·
> migrations engine is pretty poor I find this to be an odd take. The Django migrations engine is probably its strongest feature.
by qeternity 5y ago
> migrations engine is pretty poor
I find this to be an odd take. The Django migrations engine is probably its strongest feature.
- wiredfool 5y agoThere is at least one way that migrating a + b is different than migrate a + migrate b, in ways that you can then only incrementally migrate your project rather than building from scratch. It’s mainly in post migrate actions, and specifically for me adding a group for permissions.
- WD-42 5y agoIf you write manual migrations, then it's often worth it to write the reverse function (in your case, deleting that group) so that you avoid this situation.
- wiredfool 5y agoIt’s not the back and forth, it’s that a migration in b that requires the post migrate step from a will fail if both migrations are run in one shot, (say, because you’re bootstrapping a new dev or test db) but it will work when done incrementally (such as during development or deployment).
- ac130kz 5y agoAny change you make has to be atomic, or it is unable to detect the change, and you have to rely on manual migrations.