#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):
Besides the fact that it's existing production code, and using an Abstract
model would change the database structure, there actually is one reason.
A different model has a relationship to OrgUnit, and from the perspective
of that model, it's important that it doesn't need to know which of the
OrgUnit subclasses it relates to (i.e., as long as it relates to _any_
OrgUnit, that's fine).
Having said that, I'm not entirely happy with that model structure, and I
plan at some point to move it to a better structure (I have a similar
setup that allows an arbitrary number of levels of hierarchy, for
instance). However, I can't change that //right now//.
--
Ticket URL: <https://code.djangoproject.com/ticket/28110#comment:3>
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.d63f834870b0d1e82f08ae33d3ced035%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
