From de5e768557db107106bc3cfc6106055e6af842cb Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Thu, 10 Sep 2009 15:21:16 +0000 Subject: [PATCH] Fixed #11477: Generic views docs point out bug with wrong queryset Thanks SmileyChris git-svn-id: http://code.djangoproject.com/svn/django/trunk@11484 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/generic-views.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/topics/generic-views.txt b/docs/topics/generic-views.txt index c7d751a86b..beadc37a1d 100644 --- a/docs/topics/generic-views.txt +++ b/docs/topics/generic-views.txt @@ -268,9 +268,9 @@ generic view. It's very handy. However, there's actually a subtle bug here -- can you spot it? The problem has to do with when the queries in ``extra_context`` are evaluated. -Because this example puts ``Publisher.objects.all()`` in the URLconf, it will +Because this example puts ``Book.objects.all()`` in the URLconf, it will be evaluated only once (when the URLconf is first loaded). Once you add or -remove publishers, you'll notice that the generic view doesn't reflect those +remove books, you'll notice that the generic view doesn't reflect those changes until you reload the Web server (see :ref:`caching-and-querysets` for more information about when QuerySets are cached and evaluated).