#30079: Prefetch cache should be aware of database source and .using() should
not
always trigger a new query
-------------------------------------+-------------------------------------
Reporter: Mike Lissner | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution: wontfix
Keywords: prefetch, | Triage Stage:
multidatabase | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mike Lissner):
Whew, that's pretty subtle in both the old and the new versions of the
documentation. I have to confess that I don't think of chaining as the
trigger for a new queryset. I think about the query as a new trigger for a
queryset. I guess I never read this part of the documentation or didn't
take it to heart.
I don't know, I don't think we can document our way out of this behavior,
but I have no idea how difficult this is to fix technically.
--
Ticket URL: <https://code.djangoproject.com/ticket/30079#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/066.a41447b1d50e7e266f06284f22f44a40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
