From 1302fe9a35f94b37a39c2fd4c09c45f942f94de8 Mon Sep 17 00:00:00 2001 From: Malcolm Tredinnick Date: Wed, 3 Dec 2008 05:49:37 +0000 Subject: [PATCH] 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 --- 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 40ea0f9900..92e0c9c044 100644 --- a/docs/topics/cache.txt +++ b/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.