Comments on: Django – sharing a memcached instance

By: Mads Sülau Jørgensen

Mads Sülau Jørgensen — Wed, 23 Mar 2011 12:08:55 +0000

Agreed. I’ve updated the post to reflect the fact, that django 1.3 was released last night.

By: Andrew Ash

Andrew Ash — Tue, 22 Mar 2011 20:20:02 +0000

The patch that Curious User linked to has been approved in Django 1.3, which should be out shortly.

http://code.djangoproject.com/changeset/14623

http://docs.djangoproject.com/en/dev/topics/cache/#cache-key-prefixing

By: Mads Sülau Jørgensen

Mads Sülau Jørgensen — Thu, 01 Jul 2010 10:33:27 +0000

Oh, that's even better!

I'll stick it in the post, thanks again :)

By: Curious User

Curious User — Thu, 01 Jul 2010 10:31:30 +0000

Thanks for your quick reply!

Note a patch has been submitted: http://code.djangoproject.com/ticket/13795

By: Mads Sülau Jørgensen

Mads Sülau Jørgensen — Thu, 01 Jul 2010 10:26:36 +0000

If you set CACHE_MIDDLEWARE_KEY_PREFIX and use the memcached_key_prefix cache backend, both will add a key to the cache key.

So, if the CacheMiddleware were to insert a key called frontpage, it would then prefix it with the above setting, and pass it along to the cache backend, which then again prefixes the key. You then end up with a key called CACHE_MIDDLEWARE_KEY_PREFIX + cache_backend_prefix + cache_key which is suboptimal.

By: Curious User

Curious User — Thu, 01 Jul 2010 10:00:15 +0000

Please explain "kind of conflict".

I appreciate you taking the time to post this, as have countless other non-commenters.

By: Mads Sülau Jørgensen

Mads Sülau Jørgensen — Mon, 13 Jul 2009 08:04:39 +0000

Nope, that setting is only used in the cache middleware.

The above solution is for the cache layer in general, so it will actually kind of conflict with the CACHE_MIDDLEWARE_KEY_PREFIX.

By: jjjj

jjjj — Sun, 12 Jul 2009 16:17:35 +0000

http://docs.djangoproject.com/en/dev/ref/settings/#cache-middleware-key-prefix

wouldn’t this just work?