#17001: Allow usage of custom querysets in prefetch_related
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: loic84
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: prefetch_related | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Anssi Kääriäinen <akaariai@…>):
In [changeset:"7bbb6958dcb6a450f926e5bb49b07391f801aef1"]:
{{{
#!CommitTicketReference repository=""
revision="7bbb6958dcb6a450f926e5bb49b07391f801aef1"
Allowed custom querysets when prefetching single valued relations
The original patch for custom prefetches didn't allow usage of custom
queryset for single valued relations (along ForeignKey or OneToOneKey).
Allowing these enables calling performance oriented queryset methods like
select_related or defer/only.
Thanks @akaariai and @timgraham for the reviews. Refs #17001.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/17001#comment:47>
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/066.72af0a65fcb739b55e01e0c8b2b189b2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
