mirror of
https://github.com/django/django.git
synced 2025-11-07 07:15:35 +00:00
[1.6.x] Fixed #24035 -- Clarified docs on CACHE_MIDDLEWARE_KEY_PREFIX vs KEY_PREFIX
Backport of 446b50b90e from master
This commit is contained in:
committed by
Tim Graham
parent
d237aaa929
commit
70c965ad4f
@@ -411,6 +411,8 @@ of 60 seconds, and a maximum capacity of 1000 items::
|
||||
Invalid arguments are silently ignored, as are invalid values of known
|
||||
arguments.
|
||||
|
||||
.. _the-per-site-cache:
|
||||
|
||||
The per-site cache
|
||||
==================
|
||||
|
||||
@@ -537,9 +539,9 @@ setting for the middleware. It can be used like this::
|
||||
def my_view(request):
|
||||
...
|
||||
|
||||
The two settings can also be combined. If you specify a ``cache`` *and*
|
||||
a ``key_prefix``, you will get all the settings of the requested cache
|
||||
alias, but with the key_prefix overridden.
|
||||
The ``key_prefix and ``cache`` arguments may be specified together. The
|
||||
``key_prefix`` argument and the :setting:`KEY_PREFIX <CACHES-KEY_PREFIX>`
|
||||
specified under :setting:`CACHES` will be concatenated.
|
||||
|
||||
Specifying per-view cache in the URLconf
|
||||
----------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user