summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrad Fitzpatrick <brad@danga.com>2008-10-14 23:12:17 -0700
committerDustin Sallings <dustin@spy.net>2009-03-19 01:52:53 -0700
commitc619881867bfe891c6477712edec53b744f9d991 (patch)
tree7fcf8e1f4e74689b47449d1ba424b225015c085c
parent674166c002fe2e32f0385d12351091d738150a12 (diff)
downloadmemcached-c619881867bfe891c6477712edec53b744f9d991.tar.gz
update protocol docs
-rw-r--r--doc/protocol.txt11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/protocol.txt b/doc/protocol.txt
index a39a7f3..9bfe901 100644
--- a/doc/protocol.txt
+++ b/doc/protocol.txt
@@ -275,11 +275,12 @@ Increment/Decrement
Commands "incr" and "decr" are used to change data for some item
in-place, incrementing or decrementing it. The data for the item is
-treated as decimal representation of a 64-bit unsigned integer. If the
-current data value does not conform to such a representation, the
-commands behave as if the value were 0. Also, the item must already
-exist for incr/decr to work; these commands won't pretend that a
-non-existent key exists with value 0; instead, they will fail.
+treated as decimal representation of a 64-bit unsigned integer. If
+the current data value does not conform to such a representation, the
+incr/decr commands return an error (memcached <= 1.2.6 treated the
+bogus value as if it were 0, leading to confusing). Also, the item
+must already exist for incr/decr to work; these commands won't pretend
+that a non-existent key exists with value 0; instead, they will fail.
The client sends the command line: