#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
-------------------------------------+-------------------------------------
Changes (by Markus Holtermann <info@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"63f9b633f9cb620a4c4764b47dca127706a8d7b4" 63f9b633]:
{{{
#!CommitTicketReference repository=""
revision="63f9b633f9cb620a4c4764b47dca127706a8d7b4"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24725#comment:8>
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.8a3d8b1ade4c216b0530a933ff836b24%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
