#23816: Ability to defer model field by default
-------------------------------------+-------------------------------------
Reporter: rcoup | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by dfunckt):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I find this really useful, as most of the times you (myself actually,
assuming most people too) really don't make a manager just for this
optimisation. So defining deferred fields at model level makes sense for
me. Though I would prefer to specify the fields in the model's Meta
options, as a list of field names, similar to unique_together option.
--
Ticket URL: <https://code.djangoproject.com/ticket/23816#comment:1>
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.fce7836195653655c879db85ecb0f0c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
