Re:Taming the beast that is the Django ORM – An introduction
by bruce343434 on Sunday September 01, 2024 @04:44AM
(#41415295)
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.
[ Parent
| on HN ]
Re:Taming the beast that is the Django ORM – An introduction
by andybak on Sunday September 01, 2024 @04:56AM
(#41415344)
Not 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.
Re:Taming the beast that is the Django ORM – An introduction
by DarkNova6 on Sunday September 01, 2024 @07:23AM
(#41415979)
That'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.
Re:Taming the beast that is the Django ORM – An introduction
by reportgunner on Sunday September 01, 2024 @11:39AM
(#41417790)
> ..with Python mentality
As opposed to what mentality ? I mean any tool I worked with has the same problem.
Re:Taming the beast that is the Django ORM – An introduction
by Izkata on Sunday September 01, 2024 @01:48PM
(#41418778)
Not 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.
Re:Taming the beast that is the Django ORM – An introduction
by agumonkey on Sunday September 01, 2024 @07:13AM
(#41415925)
Something in the official docs or more like shared through blogs or stackoverflow ?
Re:Taming the beast that is the Django ORM – An introduction
by stavros on Sunday September 01, 2024 @07:20AM
(#41415955)
It's in the standard docs:
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.