Hey folks, I was looking at the code used to detect conflicts in migrations [1]. It seems to use a very safe approach, by avoiding with multiple node leafs in the migration graph.
While this is safe, I’ve been having some problems when it comes to scalability when having multiple migrations created in a short period of time (for the same app). Questions: 1. Are there any obvious impediments on improving the conflicts detection? 2. Does anyone have ideas on how to improve the conflict detection? (eg. going down from app-level to model-level detection) Thanks! [1] https://github.com/django/django/blob/e3f6e18513224c8ad081e5a19da641f49b0b43da/django/db/migrations/loader.py#L301-L313 -- Caio Ariede caio.ari...@gmail.com -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/FE717E60-7B66-4050-B233-20C47FBF6038%40gmail.com.
