Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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_MIDDLEVARE_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_MIDDLEVARE_KEY_PREFIXCACHE_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 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.

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.