#32294: related_name='+' doesn't work for ManyToMany fields
-------------------------------------+-------------------------------------
Reporter: Aleksey Ruban | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by Aleksey Ruban:
Old description:
> Django raises an error during creation a db migration if two models with
> the same refer to the same model in m2m field. related_name='+' or 'foo+'
> don't impact anything.
> In some my project there are 50 apps and almost each one has a model with
> the same name. So I have to come up with a related name and write it in
> for each m2m field.
> Just try to make a migration for my test project
> https://github.com/rafick1983/django_related_name_bug
New description:
Django raises an error during creation a db migration if two models with
the same name refer to the same model in m2m field. related_name='+' or
'foo+' don't impact anything.
In some my project there are 50 apps and almost each one has a model with
the same name. So I have to come up with a related name and write it in
for each m2m field.
Just try to make a migration for my test project
https://github.com/rafick1983/django_related_name_bug
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32294#comment:1>
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/068.40e92cf753a6e391828e65f5bb99d69e%40djangoproject.com.
