#24725: "ProgrammingError: relation does not exist" when renaming many-to-many
target model
-------------------------------------+-------------------------------------
Reporter: dbrgn | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.8
Severity: Release blocker | Resolution: fixed
Keywords: migrations | 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 Markus Holtermann <info@…>):
In [changeset:"bf4dc5733fec86e7dfcdeddbcf4ce047c0b2f922" bf4dc573]:
{{{
#!CommitTicketReference repository=""
revision="bf4dc5733fec86e7dfcdeddbcf4ce047c0b2f922"
[1.8.x] Fixed #24725 -- Allowed renaming of target models in ManyToMany
relations
This is a regression caused by introducing rendered migration states in
1aa3e09c2043 and the _meta refactoring in fb48eb05816b.
Thanks to Danilo Bargen for reporting the issue and Marten Kenbeek and
Tim Graham for triaging the bug and providing the initial test case.
Backport of 63f9b633f9cb620a4c4764b47dca127706a8d7b4 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24725#comment:10>
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/063.90131e3e89a22350d66e6f86ceec13f3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
