#23816: Ability to defer model field by default
-------------------------------------+-------------------------------------
Reporter: rcoup | Owner: nobody
Type: New feature | Status: new
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 willstott101):
I can see a use for this. Currently using a manager which looks at
`auto_defer` (on the manager due to
[https://code.djangoproject.com/ticket/5793 5793]).
{{{
class AutoDeferManagerMixin(object):
use_for_related_fields = True
auto_defer = tuple()
def get_queryset(self, *args, **kwargs):
return super(AutoDeferManagerMixin, self).get_queryset(*args,
**kwargs).defer(*self.auto_defer)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23816#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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.6b278a55c0deafc608c3284f86ce6adf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
