Hi,
I'm developing some applications using memcached and I saw that the
incr operation does not update the key's expiration, requiring the
usage of get + set if I want to update the expiration.
Is there a special reason to this behavior?
Thanks in advance,
Bruno Pospichil
Hi,
I'm developing some applications using memcached and I saw that the
incr operation does not update the key's expiration, requiring the
usage of get + set if I want to update the expiration.
Is there a special reason to this behavior?
It's more flexible if that's the default. you can
Updates:
Status: Fixed
Comment #1 on issue 239 by dorma...@rydia.net: Memcached Parable Cartoon
location has changed
http://code.google.com/p/memcached/issues/detail?id=239
Looks like his tag url moved from /comic/tag to just /tag, so I updated it
on the wiki. Uh, thanks :P
Comment #1 on issue 237 by dorma...@rydia.net: timedrun.c L103
http://code.google.com/p/memcached/issues/detail?id=237
what?
Updates:
Status: Invalid
Comment #3 on issue 95 by dorma...@rydia.net: Memory allocation default
change (-m 40 doesn't work)
http://code.google.com/p/memcached/issues/detail?id=95
killing this. plans are going elsewhere anyway.
Comment #2 on issue 239 by gwa...@gmail.com: Memcached Parable Cartoon
location has changed
http://code.google.com/p/memcached/issues/detail?id=239
I didn't see an edit button in the wiki, hence the ticket, but I didn't
mean to set the priority so high...
Comment #2 on issue 237 by magicboh...@gmail.com: timedrun.c L103
http://code.google.com/p/memcached/issues/detail?id=237
i think L103 should be return spawn_and_wait(argc-2, argv+2);.
the first param is argc - 2 not argc + 2.
Hi everyone,
I am new to this group. I am looking out for a very peculiar concern.
I am trying to implement memcache on Hbase. Following are my
concerns :
1. Is it practically possible ? I googled it and didn;t found a
solution for same.
2. If it is, what is it, and worth enough for the efforts
