#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 Paul Kenjora):
This ticket breaks abstraction, user defined fields now clash with
framework defined fields. In addition the framework fields are inferred
not explicit, giving the user no reasonable way to know ahead of time what
the conflict may be, especially for 3rd party models that may end up
clashing. Can we raise the severity of this since it forces a significant
project rewrite ( rename all clashing fields ) from version 1.8 to 1.9+?
I'll continue investigating, for the curious the clash is caught at:
/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-
packages/django/db/models/base.py" [readonly] line 1453
Search for E006 in file. Looks like there is already an exception for id
clash, do we add one for inherited models?
--
Ticket URL: <https://code.djangoproject.com/ticket/28110#comment:6>
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.7d970f1181d0ab5ff799f9e5914e6c5b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
