#22397: Issues removing M2M field with explicit through model
---------------------------------+------------------------------------
Reporter: melinath | Owner: andrewsg
Type: Bug | Status: assigned
Component: Migrations | Version: master
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 andrewsg):
The problem with the AttributeError seems to actually be a problem with
allowing the removal of a model that has M2M fields pointing to it at all,
so I'm going to focus on putting checks in to make sure that doesn't
happen, and also to make sure makemigrations does the right thing in that
case.
The problem with the KeyError appears to only affect sqlite and has a
straightforward fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/22397#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/066.0234840571d839fe1c5531632655eb0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
