#25044: Renaming a ManyToManyField's through table creates a broken migration
----------------------------+---------------------------------------------
Reporter: Ian-Foote | Owner: vytisb
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | 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:"b737c0f5db8fe8499d39c39d2442eaee595ca0fd" b737c0f]:
{{{
#!CommitTicketReference repository=""
revision="b737c0f5db8fe8499d39c39d2442eaee595ca0fd"
[1.10.x] Fixed #25044 -- Fixed migrations for renaming ManyToManyField's
through model.
Backport of f1e408ff40d2c1753f92515c70a44634b4d47467 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25044#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 [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/067.2dd24709ead133d66a99405f619eceaf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
