#22432: Switching model on an M2M field results in a broken db (no change to the
automatic through table)
---------------------------------+--------------------------------------
Reporter: melinath | Owner: timo
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7-beta-1
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 melinath):
Blocking this one with an error makes sense, because it's a weird edge
case (and probably shouldn't be done, honestly) but #22476 is related to
changes to fields that *don't* affect the database (blank, help_text, etc)
but still generate migrations) so it should probably still get fixed
(IMO).
--
Ticket URL: <https://code.djangoproject.com/ticket/22432#comment:6>
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.ad18f05861e6bf91d3f3c7321d518238%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
