#26676: Prefetch with to_attr shouldn't store its result in the referenced
relation
cache
-------------------------------------+-------------------------------------
Reporter: Ursidours | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: Prefetch | Triage Stage: Ready for
prefetch_related queryset | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"58f0d40b6d98bf9ad2861cf742f7b2a327cc8068" 58f0d40b]:
{{{
#!CommitTicketReference repository=""
revision="58f0d40b6d98bf9ad2861cf742f7b2a327cc8068"
[1.10.x] Fixed #26676 -- Prevented prefetching to_attr from caching its
result in through attr.
Thanks Ursidours for the report.
Backport of 53a5fb3cc0137bebeebc0d4d321dbfe20397b065 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26676#comment:5>
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/067.5ac96aa31d78286c4edc153bf727c7b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
