#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
-----------------------------+------------------------------------
Changes (by Bhuvnesh):
* owner: nobody => Bhuvnesh
* status: new => assigned
Comment:
Mariusz , if the names of models are same (but different apps), are there
any expected names of the cloumns for m2m db table? Can it be
{{{incident_id}}} and {{{incidents_incident_id}}} since two db columns
cannot have same name?
--
Ticket URL: <https://code.djangoproject.com/ticket/34250#comment:2>
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/010701859fdc6532-425c8441-fa73-4f92-a349-8d49e01db5d0-000000%40eu-central-1.amazonses.com.
