#22605: Impossible to delete two models with a M2M field
---------------------------------+----------------------------------------
Reporter: andrewgodwin | Owner: andrewgodwin
Type: Bug | Status: closed
Component: Migrations | Version: 1.7-beta-2
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+----------------------------------------
Changes (by Andrew Godwin <andrew@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"31fc34e447137631e6ea58fc33f3642e65479472"]:
{{{
#!CommitTicketReference repository=""
revision="31fc34e447137631e6ea58fc33f3642e65479472"
[1.7.x] Rewrote migration autodetector to involve actual computer science.
Fixes #22605, #22735; also lays the ground for some other fixes.
Conflicts:
django/db/migrations/autodetector.py
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22605#comment:12>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.79773028234337fe1b7f9d1ef0c08d3c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
