#22397: Issues removing M2M field with explicit through model
---------------------------------+------------------------------------
Reporter: melinath | Owner: andrewsg
Type: Bug | Status: closed
Component: Migrations | Version: master
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
---------------------------------+------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"0d397e5a5b98c475b664ff12f11729671fe1ad42"]:
{{{
#!CommitTicketReference repository=""
revision="0d397e5a5b98c475b664ff12f11729671fe1ad42"
Revert "Fixed #22397 -- Issues removing M2M field with explicit through
model."
This reverts commit 00e3b9a2a992ee0b7288eeeb03e7cbd52ebc6dce.
It's causing a regression when tested with the proxy_model_inheritance
tests.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22397#comment:10>
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.05e1b0b9546515b37d23fd34e18ff6e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.