#17673: Forbid field shadowing in model multi-inheritance
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: validation | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
The re-indentations look good to me (apart of the "clash ->
clashing_field" typo there).
I would like to get a second opinion on the validations part. There the
only controversial thing is forbidding field shadowing. But this is just
to prevent model structures which are known to be buggy. The usual example
is having two parent models, each containing the automatically created id
field in them. When you try to save such a model things will break. So,
removing this from allowed model structures should not be considered
backwards incompatible, as the structure doesn't actually work currently.
Does this need doc changes? I don't remember if we have forbidden model
attribute names section, or forbidden model structures section in the
docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/17673#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
