#31442: Inherited ManyToMany.all() empty with multiple inherited models of same
name from abstract one
-------------------------------------+-------------------------------------
Reporter: Gereon Kremer | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(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
-------------------------------------+-------------------------------------
Comment (by Gereon Kremer):
Sure, see the new attachment.
Running `./manage.py makemigrations` yields
{{{
SystemCheckError: System check identified some issues:
ERRORS:
appA.Stuff.owners: (fields.E305) Reverse query name for 'Stuff.owners'
clashes with reverse query name for 'Stuff.owners'.
HINT: Add or change a related_name argument to the definition for
'Stuff.owners' or 'Stuff.owners'.
appB.Stuff.owners: (fields.E305) Reverse query name for 'Stuff.owners'
clashes with reverse query name for 'Stuff.owners'.
HINT: Add or change a related_name argument to the definition for
'Stuff.owners' or 'Stuff.owners'.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31442#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/063.3ab6bd807f3c7d1651c793a7fbae0119%40djangoproject.com.
