#23091: Squashed migrations may try to add existing constraint if there was RunPython between create and alter some-model migrations -------------------------------+-------------------------------------- Reporter: anonymous | Owner: nobody Type: Uncategorized | Status: new Component: Migrations | Version: 1.7-rc-1 Severity: Normal | Resolution: Keywords: | Triage Stage: Unreviewed Has patch: 0 | Needs documentation: 0 Needs tests: 0 | Patch needs improvement: 0 Easy pickings: 0 | UI/UX: 0 -------------------------------+--------------------------------------
Comment (by riklaunim): The problem is with the constraint being re-added. I'll try to provide a migration flow to reproduce it. -- Ticket URL: <https://code.djangoproject.com/ticket/23091#comment:3> Django <https://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/067.14b6d19565b1327108e7fa983b57a8ae%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.