diff options
| author | James Bennett <ubernostrum@gmail.com> | 2011-09-11 05:57:38 +0000 |
|---|---|---|
| committer | James Bennett <ubernostrum@gmail.com> | 2011-09-11 05:57:38 +0000 |
| commit | 7f45651f8db35a9f5cd5a5822c133cefb607aa40 (patch) | |
| tree | 9a2d0bf2cb3e6daa46cfbf42c2171d8bd8e3ed83 /docs | |
| parent | 4224127b54a7faa31da00b8eb1d2f04eb8aa0746 (diff) | |
Fixed #16334: Make it quite clear that cache_page's 'cache' argument refers to the name of a cache in the CACHES setting.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@16815 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/cache.txt | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 4518353e15..d3fa888f48 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -527,9 +527,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): |
