I agree, it really depends on your project's workflow and organization as
to how often you see migration conflicts and whether this is the right way
to show them to users. Creating lock files in django core would just add
confusion for 99% of projects.
On 24 May 2017 at 23:03, Florian Apolloner w
On Wednesday, May 24, 2017 at 9:42:20 PM UTC+2, Andrew Godwin wrote:
>
> I am personally unsure about this - it's extra overhead for smaller Django
> sites, and something that larger teams could easily adopt themselves.
>
Yeah, I do not see an immediate need for this either.
--
You received th
I am personally unsure about this - it's extra overhead for smaller Django
sites, and something that larger teams could easily adopt themselves. I
think it might make more sense as a third-party app that plugs in?
Andrew
On Wed, May 24, 2017 at 12:39 PM, wrote:
> To elaborate on this feature re
To elaborate on this feature request:
When working on a Django project with other people, a common issue is
unintentionally creating conflicting migrations. These happen silently if
two developers create and merge migrations in parallel. It's not clear
there is a problem until after the second
Hi!
This is an idea that has been around for a while, and has been implemented
by various organizations running Django: using lock files to prevent
migration conflicts.
I recently implemented something for our Django project at work. Here is a
cleaned-up version:
https://github.com/django/django
