Browse files

[1.0.X] Fixed #9740 -- Updated and correct usage of max_entries in ca…

…che documentation.

Backport of r9556 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@9559 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent a261602 commit 500021a9233dee9a4bd1fc6c88a586d720905f89 @malcolmt malcolmt committed Dec 3, 2008
Showing with 4 additions and 3 deletions.
  1. +4 −3 docs/topics/cache.txt
View
7 docs/topics/cache.txt
@@ -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.

0 comments on commit 500021a

Please sign in to comment.