5 ms·
We've had serious trouble with migration merges when two people work on different parts of the code, yet in the same module, and they both generate a "migration
by bruce343434 2y ago
We've had serious trouble with migration merges when two people work on different parts of the code, yet in the same module, and they both generate a "migration nr. 6" on their feature branches.
- andybak 2y agoNot at my desk but from memory, this is a something with a clearly documented "solution". I put that word in quotes because I don't want to imply it's a problem - it's just something you need to know how to handle.
- agumonkey 2y agoSomething in the official docs or more like shared through blogs or stackoverflow ?
- stavros 2y agoIt's in the standard docs: https://docs.djangoproject.com/en/5.1/topics/migrations/#version-control https://docs.djangoproject.com/en/5.1/topics/migrations/#ver... You just rename one of the two files, and add the dependency. If they touch the same fields, you obviously have to resolve that manually.
- DarkNova6 2y agoThat's the problem I have with Python mentality. Everything is great, you just need to know about the myriad of pitfalls and problems. A good environment makes problems obvious and and allows to communicate decisions clearly. This is the trap of the local maximum.
- reportgunner 2y ago> ..with Python mentality As opposed to what mentality ? I mean any tool I worked with has the same problem.
- Izkata 2y agoNot that, this is the problem they're referring to: > > Everything is great, you just Part of the python mentality is to pretend difficulties aren't there in order to keep presenting itself as beginner-friendly.
- helpfulContrib 2y ago[dead]