Switch to using ForwardingCacheBackend for all cache requests.
Review Request #6482 — Created Oct. 21, 2014 and submitted
We now force ForwardingCacheBackend as the default cache backend, and
instead work with the 'forwarded_backend' cache name when looking up or
saving the real cache backend.This covers the configuration forms, cache stats, and initial settings
population.
Successfully loaded my cache settings.
Switched caches in the UI and reloaded the stats page. Saw that it
immediately updated for the current cache settings.Started up memcached in verbose mode. Switched from local memory caching
to memcached and immediately saw operations on memcached.
Description | From | Last Updated |
---|---|---|
'django_reset' imported but unused |
reviewbot | |
Can me merge this with the stuff below? It seems weird to set CACHES['default'] here and then change it later. |
david | |
'from settings_local import *' used; unable to detect undefined names |
reviewbot | |
'PIPELINE_CSS' imported but unused |
reviewbot | |
'PIPELINE_JS' imported but unused |
reviewbot | |
'django_reset' imported but unused |
reviewbot | |
'from settings_local import *' used; unable to detect undefined names |
reviewbot | |
'PIPELINE_CSS' imported but unused |
reviewbot | |
'PIPELINE_JS' imported but unused |
reviewbot |
- Change Summary:
-
Improve the comments to make it more clear what we're doing with CACHES.
- Commit:
-
1b35ea3c5b544abc27ecad59e9871b1342629bb2cd034a87d34e53f0be1dc8bf47c10e82c065c34d