delete() unexpected behavior (bug?)

[GoogleCodeExporter]

delete() unexpected behavior (bug?)

[GoogleCodeExporter]

You're deleting with reservation so your add is failing.  This functionality 
has been
removed in newer versions of memcached, but it was designed specifically to 
provide
this functionality.

You should be checking the results of your ops.  You would see the adds failing 
here.

Original comment by [email protected] on 25 Mar 2009 at 5:50

• Changed state: Invalid

[GoogleCodeExporter]

> You're deleting with reservation so your add is failing.
1. First operation is $memcache->delete($k); it has no delay.
2. I thought, delete(k,n) sets expiration time to time()+n.

Thanks.

Original comment by [email protected] on 25 Mar 2009 at 7:20

[GoogleCodeExporter]

Check the return of that delete.  It probably returned NOT_FOUND.

No, the delete with timeout was specifically to ``lock'' a key from adds.  Its
semantics were confusing with flush_all's delay.  Unfortunately flush_all won 
and the
delete with timeout got removed.

Original comment by [email protected] on 25 Mar 2009 at 8:08

[GoogleCodeExporter]

Thank for you very much.
Is it possible to change Time-To-Life of the existing object?

Original comment by [email protected] on 25 Mar 2009 at 8:54