#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 Loic Bistuer <loic.bistuer@…>): In [changeset:"870b0a1f8689aa8fd4806623262228b8ac3a88a5"]: {{{ #!CommitTicketReference repository="" revision="870b0a1f8689aa8fd4806623262228b8ac3a88a5" Fixed the ordering of prefetch lookups so that latter lookups can refer to former lookups. Thanks Anssi Kääriäinen and Tim Graham for the reviews. Refs #17001 and #22650. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/17001#comment:49> 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.1aa3ff698bb38d1017087234cf79c34d%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.