#34250: Duplicate model names in M2M relationship causes RenameModel migration
failure
-----------------------------+---------------------------------------------
Reporter: Zac Miller | Owner: Bhuvnesh
Type: Bug | Status: closed
Component: Migrations | Version: 4.1
Severity: Normal | Resolution: fixed
Keywords: RenameModel | 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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"5cde08f702c1db7646c0c1c8f9d72d01067310df" 5cde08f7]:
{{{
#!CommitTicketReference repository=""
revision="5cde08f702c1db7646c0c1c8f9d72d01067310df"
[4.2.x] Fixed #34250 -- Fixed renaming model with m2m relation to a model
with the same name.
Backport of ff3a2834224f527ca574b5cd0d578c8c26d51a6c from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34250#comment:16>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018650233dc0-e42cc370-d8b1-48c6-b544-34fc13b05f88-000000%40eu-central-1.amazonses.com.
