#28110: Model inheritance field name collision check error refers to related
accessors as fields
--------------------------------------+------------------------------------
Reporter: Matthew Schinckel | Owner: nobody
Type: Bug | Status: new
Component: Core (System checks) | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Matthew Schinckel):
Hmm. The documentation at
https://docs.djangoproject.com/en/1.11/topics/db/models/#inheritance-and-
reverse-relations suggests that it should already give a more informative
error.
Reading more carefully, that seems to be a M2M relationship to the parent,
however in this case it's an FK to a "sibling" model (even though in this
specific case there is a hierarchy, but I think that's irrelevant).
I think that this error message (or something very similar) should be used
for the situation I managed to find myself in.
--
Ticket URL: <https://code.djangoproject.com/ticket/28110#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.3aa25025bcf92099484f63835ca2a9da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
