Re: memcached backed

2007-01-30 Thread David S.
On Jan 30, 12:16 pm, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > Django's cache only implements a minimal subset of functions -- those > supported by *all* cache backends. You can always interact with the memcached > directly For example we clear memcached like this: from django.core.cac

Re: memcached backed

2007-01-30 Thread Jacob Kaplan-Moss
On 1/29/07 9:31 PM, Isaac Sparrow wrote: > I think Mark is referring to the actual 'replace' functionality of > memcached. From http://www.danga.com/memcached/ > > replace -- sets in the cache only if the key already exists > > As opposed to: > > set -- unconditionally sets a given key with a g

Re: memcached backed

2007-01-29 Thread Isaac Sparrow
I think Mark is referring to the actual 'replace' functionality of memcached. From http://www.danga.com/memcached/ replace -- sets in the cache only if the key already exists As opposed to: set -- unconditionally sets a given key with a given value Isaac On 1/29/07, Jacob Kaplan-Moss <[EMAIL

Re: memcached backed

2007-01-29 Thread Jacob Kaplan-Moss
On 1/28/07 8:08 PM, [EMAIL PROTECTED] wrote: > why doesn't the memcached backend support 'replace'? I'm not sure what you mean:: >>> cache.set("key", "val1") >>> cache.get("key") "val1" >>> cache.set("key", "val2") >>> cache.get("key") "val2" Isn'

memcached backed

2007-01-29 Thread [EMAIL PROTECTED]
why doesn't the memcached backend support 'replace'? thanks mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscrib