#28586: Automatically prefetch related for "to one" fields as needed.
-------------------------------------+-------------------------------------
Reporter: Gordon Wrigley | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: prefetch_related | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Gordon Wrigley):
For curiosity sake I tried running the test suite with
auto_prefetch_related enabled by default. There were 3 test failures, two
were looking for queries that are removed by auto_prefetch_related.
The third attempts to fetch more rows than the sqlite backend can handle
in a single 'in' clause, which I'd think is an issue with the 'in'
implementation.
Looking at the test it is currently unintentionally doing some four and a
quarter thousand DB queries. And attempting to fix it with an explicit
prefetch fails in the exact same manner as the automatic prefetch.
--
Ticket URL: <https://code.djangoproject.com/ticket/28586#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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.731d8d0558c3960c85d425590688a488%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
