Author: mtredinnick
Date: 2008-12-02 23:49:37 -0600 (Tue, 02 Dec 2008)
New Revision: 9556
Modified:
django/trunk/docs/topics/cache.txt
Log:
Fixed #9740 -- Updated and correct usage of max_entries in cache documentation.
Modified: django/trunk/docs/topics/cache.txt
===================================================================
--- django/trunk/docs/topics/cache.txt 2008-12-03 00:44:12 UTC (rev 9555)
+++ django/trunk/docs/topics/cache.txt 2008-12-03 05:49:37 UTC (rev 9556)
@@ -213,8 +213,9 @@
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 ``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.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
