#22397: Issues removing M2M field with explicit through model
---------------------------------+------------------------------------
Reporter: melinath | Owner: andrewsg
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
---------------------------------+------------------------------------
Comment (by loic84):
No problem, actually I think it's a good opportunity to investigate, I
suspect we have a few issues with testing at the intersection of app-
loading and migrations.
I'm pretty sure I had this issue in passing ("table already exist") when
figuring out #22459.
--
Ticket URL: <https://code.djangoproject.com/ticket/22397#comment:13>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.4c173f87654d24204d2cf0ac43728677%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
