#17001: Allow usage of custom querysets in prefetch_related
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: loic84
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: prefetch_related | Needs documentation: 1
Has patch: 1 | Patch needs improvement: 1
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by charettes):
In the light of @akaariai's comment concerning kwargs the only other
alternative I could think of was to rely on a `Prefetch` instance creation
counter to sort `kwargs` but as @loic84 pointed out in IRC it would be
quite fragile.
I'd say I also favor the `to_attr` approach since it looks like the most
sane way to avoid chaining `prefetch_related` to declare an ordering.
--
Ticket URL: <https://code.djangoproject.com/ticket/17001#comment:35>
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.b5619a5d926c1a0609a5810ec5912c9c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
