#25344: Document that prefetch_related() cache doesn't change unless it's
refetched
from the database
--------------------------------------+------------------------------------
Reporter: TankOs | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: prefetch_related | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* component: Database layer (models, ORM) => Documentation
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I don't think it's a good idea to change the behavior, so I'll accept as a
documentation patch. Especially for custom `Prefetch`'s it's probably
impossible to implement correct behavior "in-memory" (e.g. if `Prefetch`
has a custom queryset, we'd have to determine if the new object matches
it). Feel free to raise the issue on the DevelopersMailingList if you feel
I'm wrong.
--
Ticket URL: <https://code.djangoproject.com/ticket/25344#comment:3>
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/064.be618c2642469f88e337c864d60c20de%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
