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 given value
Ah, I see. Django's cache only implements a minimal subset of functions -- those supported by *all* cache backends. You can always interact with the memcached directly if you need "replace" (though frankly I can't see why...) Jacob --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
