#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 akaariai):
Sorry for bringing this up :)
What you describe seems like a sane default. We can offer hooks for users
to do all the dirty work in case they want real classes as composite
values, but I don't see a need for Django to include this stuff out of the
box.
--
Ticket URL: <https://code.djangoproject.com/ticket/16508#comment:13>
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.ffa192c4527356129bff4c29c545fba6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
