#22397: Issues removing M2M field with explicit through model
---------------------------------+------------------------------------
Reporter: melinath | Owner: nobody
Type: Bug | Status: new
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
---------------------------------+------------------------------------
Changes (by loic84):
* cc: loic@… (added)
* version: 1.7-beta-1 => master
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Didn't have time to work on a fix, but I could reproduce.
Wrote some test cases for removal of M2M fields:
https://github.com/django/django/pull/2527.
`test_remove_field_m2m_with_through1` and
`test_remove_field_m2m_with_through2` reproduce the two issues from the
ticket description.
--
Ticket URL: <https://code.djangoproject.com/ticket/22397#comment:3>
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.0653c489b07e0c833d7c5d13f27ce167%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
