#28723: RelatedManager.get_prefetch_queryset returns "wrong" cache_name
-------------------------------------+-------------------------------------
Reporter: Mike Hansen | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"8b21878357364a461bae711c4d0011a8f338b160" 8b218783]:
{{{
#!CommitTicketReference repository=""
revision="8b21878357364a461bae711c4d0011a8f338b160"
Refs #28723 -- Fixed stale prefetch_related cache after add/remove.
Regression in 514b2c989a948e3c59bda0da0c9427acf643cf5b.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28723#comment:8>
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.ee181d78f2f2a853781896d5bc6bfce6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
