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 PROTECTED]> wrote:
>
> 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't that "replace"?
>
> Jacob
>
> >
>
--
Random Geek Stuff: http://l0wbyt3.blogspot.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
