Revision history [back]
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using CACHE_MIDDLEWARE_KEY_PREFIX
setting, in 1.3 - the setting was changed to a member of cache key dictionary called KEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using CACHE_MIDDLEWARE_KEY_PREFIX
setting, in 1.3 - the setting was changed to a member of cache key dictionary called KEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using CACHE_MIDDLEWARE_KEY_PREFIX
setting, in 1.3 - the setting was changed to a member of cache key dictionary called KEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.
Here is Django document about the cache system.
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using CACHE_MIDDLEWARE_KEY_PREFIX
setting, in 1.3 - the setting was changed to a member of cache key dictionary called KEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.page.
Here is Django document about the cache system.
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using CACHE_MIDDLEWARE_KEY_PREFIX
setting, in 1.3 - the setting was changed to a member of cache key dictionary called KEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.
Here is Django document about the cache system.
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using CACHE_MIDDLEWARE_KEY_PREFIX
setting, in 1.3 - the setting was changed to a member of cache key dictionary called KEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.
Here is Django document about the cache system.
In version 1.3 they've slightly changed the way the cache settings are structured:
The old way te set it up to version 1.2 - by using
setting, in 1.3 - the setting was changed to a member of cache key dictionary called CACHE_MIDDLEWARE_KEY_PREFIXCACHE_MIDDLEVARE_KEY_PREFIXKEY_PREFIX
.
Django 1.3 and above supports use of multiple cache stores, take a look at the doc page.