#20577: Make prefetch_related faster by lazily creating related querysets
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
#19264 was a duplicate. In addition #20880 (splitted clone()) tracks
splitting clone() to pre_next_op() and clone() parts. That seems to be a
pre-requisite for the chain_ops() approach.
--
Ticket URL: <https://code.djangoproject.com/ticket/20577#comment:4>
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.2a11c0f7f376ad8698362118e6063fa3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
