#24749: contribute_to_class(virtual_only=True) is ignored
-------------------------------------+-------------------------------------
Reporter: hampsterx | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
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 timgraham):
Anssi said this parameter may be misnamed:
If I recall correctly the real significance of virtual_only is that
fields added with this flag are copied to child models. Generic relations
need this as they need to know the model they are used on. Normal fields
are not copied, instead they are fetched directly from the parent model
when _meta is queried. [[BR]] [[BR]]
So, it might be possible to rename virtual_only to something like
copy_to_childs, and then virtuality of a field would be determined only on
it having a column.
https://groups.google.com/d/msg/django-developers/nkEuOnIf4Ao/IPp5E11WXDkJ
--
Ticket URL: <https://code.djangoproject.com/ticket/24749#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.f199c61520aa0c12a7cc3691dd9e5e45%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
