#34250: Duplicate model names in M2M relationship causes RenameModel migration
failure
-----------------------------+------------------------------------
Reporter: Zac Miller | Owner: Bhuvnesh
Type: Bug | Status: assigned
Component: Migrations | Version: 4.1
Severity: Normal | Resolution:
Keywords: RenameModel | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+------------------------------------
Comment (by Zac Miller):
I did some further testing and you don't encounter the same issue going in
the other direction. For example, in the demo project if I rename
incidents.Incident the migration generated works fine and properly updates
the M2M on vault.Incident. The M2M table is updated and the from/to are
removed from both. After that you can do a rename on the model with the
M2M. Just an FYI for anyone who might be looking for a work around.
--
Ticket URL: <https://code.djangoproject.com/ticket/34250#comment:3>
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/01070185a13009ef-4d6fba36-6d86-4698-ae64-356d5cda7527-000000%40eu-central-1.amazonses.com.
