Herc wrote: > - The most intriguing issue I've been buffled about is the following: > How to store SQL results. For example, say I store SELECTs as md5 into > memcache. Then say at some point in the code, an UPDATE is executed. > How can I determine which memcache keys (that is, which SELECTs) > should be invalidated?? Is there a framework or some way that do this > gracefully? Or should I use memcache only for queries that do not need > be updated immediately, but can update after they expire?
I haven't found a (scalable, partition-tolerant) framework for that yet, but I happened to have just posted a blog entry with the 6 solutions I could come up with. Feel free to steal any idea therein: http://www.aminus.org/blogs/index.php/fumanchu/2007/12/30/memcached_set_invalidation Robert Brewer [EMAIL PROTECTED]
