#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
-----------------------------+---------------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ff3a2834224f527ca574b5cd0d578c8c26d51a6c" ff3a283]:
{{{
#!CommitTicketReference repository=""
revision="ff3a2834224f527ca574b5cd0d578c8c26d51a6c"
Fixed #34250 -- Fixed renaming model with m2m relation to a model with the
same name.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34250#comment:15>
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/0107018650231804-bd50429f-ae58-42f2-8808-c4448349f661-000000%40eu-central-1.amazonses.com.
