#22605: Impossible to delete two models with a M2M field
---------------------------------+--------------------------------------
Reporter: andrewgodwin | Owner: andrewsg
Type: Bug | Status: assigned
Component: Migrations | Version: master
Severity: Release blocker | 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 andrewsg):
I have a prototype autodetector-based solution, but I'm not happy with it
-- it adds a substantial bit of code to the monolithic _detect_chagnes
function (similar to how the autodetector has a 3.1-phase process for
adding models, it becomes a two or three phase process for removing
models). I'll want to consult with a core dev before going further down
this path, because I don't know how complex the alternative state_forward-
based solution would be.
--
Ticket URL: <https://code.djangoproject.com/ticket/22605#comment:5>
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.d2572d4d05473e2ce2d918d2211e972a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
