On Saturday, November 19, 2011, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Thanks for the reply Russ.
> I think ultimately it comes down to the fact that it was difficult to
figure out what was happening, where as the actual fix itself (as you
mentioned belo
Thanks for the reply Russ.
I think ultimately it comes down to the fact that it was difficult to
figure out what was happening, where as the actual fix itself (as you
mentioned below) is a simple 2 or 3 line code change.
Now that I've thought about it more, I totally agree that my original
sugges
On Sat, Nov 19, 2011 at 4:08 PM, Cal Leeming [Simplicity Media Ltd]
wrote:
> Hi,
> Since the release of 1.3, Django has changed the way it generates the
> memcache key name.
> If I was to do:
> cache.set('hello', 'world', 300)
> It would actually store the result as ":1:hello". Obviously, this is
Hi,
Since the release of 1.3, Django has changed the way it generates the
memcache key name.
If I was to do:
cache.set('hello', 'world', 300)
It would actually store the result as ":1:hello". Obviously, this is
because the version number is stored, along with the key prefix.
But, this inherentl
