#22605: Impossible to delete two models with a M2M field
---------------------------------+--------------------------------------
Reporter: andrewgodwin | Owner: nobody
Type: Bug | Status: new
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
---------------------------------+--------------------------------------
Changes (by andrewgodwin):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not yet sure how to fix this, but noting it here for posterity while I
fix something else. I suspect we may need the DeleteModel's state_forward
to remove ForeignKey references to the model as well, or at least neuter
them somehow.
The reason this doesn't happen for the creation case is that
makemigrations recognised the problem and split the creation of M2M into
two operations. A similar method could also be used as an alternative
approach.
--
Ticket URL: <https://code.djangoproject.com/ticket/22605#comment:1>
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.570a73fb67de116575d600d4fd1808c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
