p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #9740 -- Updated and correct usage of max_entries in cache documentation. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@9556 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2008-12-03 05:49:37 +00:00
parent 9ec9936413
commit 1302fe9a35
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/topics/cache.txt
View File

@ -213,8 +213,9 @@ All caches may take arguments. They're given in query-string style on the
minutes (300 seconds).
max_entries
For the simple and database backends, the maximum number of entries
allowed in the cache before it is cleaned. Defaults to 300.
For the ``locmem``, ``filesystem`` and ``database`` backends, the
maximum number of entries allowed in the cache before it is cleaned.
Defaults to 300.
cull_percentage
The percentage of entries that are culled when max_entries is reached.
@ -231,7 +232,7 @@ In this example, ``timeout`` is set to ``60``::
In this example, ``timeout`` is ``30`` and ``max_entries`` is ``400``::
CACHE_BACKEND = "memcached://127.0.0.1:11211/?timeout=30&max_entries=400"
CACHE_BACKEND = "locmem:///?timeout=30&max_entries=400"
Invalid arguments are silently ignored, as are invalid values of known
arguments.