#26916: Prefetch's to_attr does not write into cached_properties in 1.10
-------------------------------------+-------------------------------------
Reporter: karyon | Owner: charettes
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| 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:"dcf0a35b088ba9ce8907d8f34178bd6dffc27022" dcf0a35]:
{{{
#!CommitTicketReference repository=""
revision="dcf0a35b088ba9ce8907d8f34178bd6dffc27022"
[1.10.x] Fixed #26916 -- Fixed prefetch_related when using a
cached_property as to_attr.
Thanks Trac alias karyon for the report and Tim for the review.
Backport of 271bfe65d986f5ecbaeb7a70a3092356c0a9e222 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26916#comment:7>
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/064.9f6d1b3365fb417cce7911dae95fbb09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
