#22605: Impossible to delete two models with a M2M field
---------------------------------+--------------------------------------
Reporter: andrewgodwin | Owner: andrewsg
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by andrewgodwin):
andrewsg: I have been mulling re-architecting the autodetector to fix this
and a slew of other dependency bugs, so I think the solution may lie down
that road (in particular, I want to change the autodetector to be two-
phase; that is, it works out the changes to make, and then re-orders and
sorts them so the dependencies line up).
Given that, I'm not sure it would be a good idea to do any further work
here, unless you want to; would you mind if I took over the ticket? I'd
appreciate any code you have so far though, as I can probably use it!
--
Ticket URL: <https://code.djangoproject.com/ticket/22605#comment:7>
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.a7bf03df7adb0266b6a799c2d4924339%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
