Fixed #23023 -- Added warning against local-memory cache.

Thanks django at kerz.id.au.
This commit is contained in:
Tim Graham 2014-07-16 12:32:57 -04:00
parent 5954aa6db0
commit 7d0519c725
1 changed files with 3 additions and 1 deletions

View File

@ -64,7 +64,9 @@ sure you've configured your cache; see the :doc:`cache documentation
cache backend. The local-memory cache backend doesn't retain data long cache backend. The local-memory cache backend doesn't retain data long
enough to be a good choice, and it'll be faster to use file or database enough to be a good choice, and it'll be faster to use file or database
sessions directly instead of sending everything through the file or sessions directly instead of sending everything through the file or
database cache backends. database cache backends. Additionally, the local-memory cache backend is
NOT multi-process safe, therefore probably not a good choice for production
environments.
If you have multiple caches defined in :setting:`CACHES`, Django will use the If you have multiple caches defined in :setting:`CACHES`, Django will use the
default cache. To use another cache, set :setting:`SESSION_CACHE_ALIAS` to the default cache. To use another cache, set :setting:`SESSION_CACHE_ALIAS` to the