From 1ef544f91f0d4be3f44ae7fd0498530e57a9b160 Mon Sep 17 00:00:00 2001 From: David Hoffman Date: Sat, 26 Jul 2014 10:00:48 -0400 Subject: [PATCH] [1.7.x] Fixed #22553 -- Added refreshing queryset info to docs. Backport of 6d5daa30cf from master --- docs/ref/models/querysets.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 93aaaaf8107..c98c1290c06 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -721,6 +721,11 @@ can be useful in situations where you might want to pass in either a model manager or a ``QuerySet`` and do further filtering on the result. After calling ``all()`` on either object, you'll definitely have a ``QuerySet`` to work with. +When a ``QuerySet`` is :ref:`evaluated `, it +typically caches its results. If the data in the database might have changed +since a ``QuerySet`` was evaluated, you can get updated results for the same +query by calling ``all()`` on a previously evaluated ``QuerySet``. + select_related ~~~~~~~~~~~~~~