#16508: Provide real support for virtual fields
-------------------------------------+-------------------------------------
Reporter: vzima | Owner: pirosb3
Type: New feature | Status: assigned
Component: Database layer | Version: master
(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 collinanderson):
I believe in the _meta refactor we simply defined it as "doesn't add or
alter columns in the database.", something like field.column = None. It
probably does correlates to one or multiple concrete fields, but it
doesn't have to.
Also, one thing to note is that we don't want to distinguish (too much)
between virtual and non virtual on the higher levels of the API (like
Model Forms). Model Forms shouldn't care whether a field has a column in
the database or not. So in that case, it doesn't make sense to have a
_meta.virtual_fields like we used to do. But of course the ORM and
migrations are going to want to know that they should ignore these fields.
--
Ticket URL: <https://code.djangoproject.com/ticket/16508#comment:9>
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/063.f9ab43326d43958b9d229a7c17841146%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
