From 2c8e45e1f4a85691cb6349b37d4340ab8e33b023 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Sun, 11 Sep 2011 05:58:34 +0000 Subject: [PATCH] [1.3.X] Fixed #16334: Make it quite clear that cache_page's 'cache' argument refers to the name of a cache in the CACHES setting. Backport of [16815] from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@16816 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/cache.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 8ef4ea2f30..fe50160ccc 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -526,9 +526,10 @@ you may expect. But once a particular URL (e.g., ``/foo/23/``) has been requested, subsequent requests to that URL will use the cache. ``cache_page`` can also take an optional keyword argument, ``cache``, -which directs the decorator to use a specific cache alias when caching view -results. By default, the ``default`` alias will be used, but you can specify -any cache alias you want:: +which directs the decorator to use a specific cache (from your +:setting:`CACHES` setting) when caching view results. By default, the +``default`` cache will be used, but you can specify any cache you +want:: @cache_page(60 * 15, cache="special_cache") def my_view(request):