#23938: changing a ManyToManyField to a CharField while also deleting the model
being connected to breaks migrations
-------------------------------------+-------------------------------------
Reporter: hoylemd | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"79645529e7ce03a7eef1e51e7058a9880f83efb5"]:
{{{
#!CommitTicketReference repository=""
revision="79645529e7ce03a7eef1e51e7058a9880f83efb5"
Revert "[1.7.x] Fixed #23938 -- Added migration support for m2m to
concrete fields and vice versa"
This reverts commit 1702bc52cc20ed0729893177fc8f4391b4b3183c.
This doesn't work on stable/1.7.x because #23844 wasn't backported and
we're
not willing to do so because it's a large change.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23938#comment:9>
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/065.8368b46b8d9d4a3b1b7bd8f2a1b51b55%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
