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 migration is merged. With this patch, the second migration will be prevented from merging by the VCS due to a merge conflict in the lock file.
A documented example of a team that uses something like this in production can be found at the Zenefits engineering blog <https://engineering.zenefits.com/2015/11/using-old-ideas-to-solve-new-problems/> . Do you think that this is a useful feature to have in Django? And if so, does the proposed patch <https://github.com/django/django/compare/master...jianli:migration-lock-file> suffice? -Jian On Wednesday, May 17, 2017 at 1:30:41 PM UTC-7, Jian Li wrote: > > 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/compare/master...jianli:migration-lock-file > > Hopefully this is useful enough to be merged upstream. Please let me know > what you think, and keep up the amazing work! > > -Jian > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/98310105-15e4-473f-acab-e9e7b0427250%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
