diff --git a/TODO b/TODO index 4cfc6e4c39ea185edffbf5852de8318b944af201..74f133476b77abea9bbc6ec4b49d1123874954a3 100644 --- a/TODO +++ b/TODO @@ -1,12 +1,5 @@ Redis TODO and Roadmap -VERSION 1.2 TODO (Zsets, Integer encoding, Append only journal) -=============================================================== - -Most of the features already implemented for this release. The following is a list of the missing things in order to release the first beta tar.gz: - -* Continue adding tests accordingly to gcov output. - VERSION 1.4 TODO (Hash type) ============================ diff --git a/doc/CommandReference.html b/doc/CommandReference.html index b2586d16ac4ca854b9db2b3b6055f54b32b6b371..ec0376d49b67ceddd234c045da004f840527bb03 100644 --- a/doc/CommandReference.html +++ b/doc/CommandReference.html @@ -31,7 +31,7 @@

Commands operating on string values

Commands operating on lists

Commands operating on sets

-

Commands operating on sorted sets (zsets, Redis version >

1.1) ==

+

Commands operating on sorted sets (zsets, Redis version >

1.1) ==

Sorting

Persistence control commands

Remote server control commands

diff --git a/doc/KeysCommand.html b/doc/KeysCommand.html index 0b64d1a875c5268d9dd5a427a9885438ed074149..f1a6e070c608212bac34609ec64704f416e94cbf 100644 --- a/doc/KeysCommand.html +++ b/doc/KeysCommand.html @@ -28,11 +28,11 @@
#sidebar GenericCommandsSidebar

KEYS _pattern_

Time complexity: O(n) (with n being the number of keys in the DB, and assuming keys and pattern of limited length)
Returns all the keys matching the glob-style pattern asspace separated strings. For example if you have in thedatabase the keys "foo" and "foobar" the command "KEYS foo*"will return "foo foobar".
-
Note that while the time complexity for this operation is O(n)the constant times are pretty low. For example Redis runningon an entry level laptop can scan a 1 million keys databasein 40 milliseconds. Still it's better to consider this one ofthe slow commands that may ruin the DB performance if not usedwith care.
+
Note that while the time complexity for this operation is O(n)the constant times are pretty low. For example Redis runningon an entry level laptop can scan a 1 million keys databasein 40 milliseconds. Still it's better to consider this one of +
the slow commands that may ruin the DB performance if not usedwith care*.
+
In other words this command is intended only for debugging and *special* operations like creating a script to change the DB schema. Don't use it in your normal code. Use Redis Sets in order to group together a subset of objects.
Glob style patterns examples: -
  • h?llo will match hello hallo hhllo
  • hllo will match hllo heeeello -
    * haello will match hello and hallo, but not hillo
    Use \ to escape special chars if you want to match them verbatim.

    Return value

    Bulk reply, specifically a string in the form of space separated list of keys. Note that most client libraries will return an Array of keys and not a single string with space separated keys (that is, split by " " is performed in the client library usually). -
+
* h?llo will match hello hallo hhllo* h*llo will match hllo heeeello* h[ae]llo will match hello and hallo, but not hillo
Use \ to escape special chars if you want to match them verbatim.

Return value

Bulk reply, specifically a string in the form of space separated list of keys. Note that most client libraries will return an Array of keys and not a single string with space separated keys (that is, split by " " is performed in the client library usually).
diff --git a/doc/SortedSetCommandsSidebar.html b/doc/SortedSetCommandsSidebar.html index d52a788b9eab3cc12e53315833720fa5f1298727..7b722e95140780db9b767e7a09c3f6374a5b1987 100644 --- a/doc/SortedSetCommandsSidebar.html +++ b/doc/SortedSetCommandsSidebar.html @@ -26,7 +26,7 @@
- == Sorted Set Commands ==

+ == Sorted Set Commands ==

diff --git a/doc/SponsorshipHistory.html b/doc/SponsorshipHistory.html index ff81c872793c5afecd9d920ce8f31c09e7711356..97616db9e755930dd48263621edcc4a84c050122 100644 --- a/doc/SponsorshipHistory.html +++ b/doc/SponsorshipHistory.html @@ -26,7 +26,9 @@
-

Redis Sponsorship History

This is a list of companies that sponsorship Redis developments, with details about the sponsored features. Thanks for helping the project!.

If your company is considering a sponsorship please read the How to Sponsor page.

+

Redis Sponsorship History

This is a list of companies that sponsorship Redis developments, with details about the sponsored features. Thanks for helping the project!.

If your company is considering a sponsorship please read the How to Sponsor page.

+Also thaks to the following people or organizations that donated to the Project: +
diff --git a/doc/ZincrbyCommand.html b/doc/ZincrbyCommand.html new file mode 100644 index 0000000000000000000000000000000000000000..7e6a8458aa579663f4dac03d4726c60e0c7ad15a --- /dev/null +++ b/doc/ZincrbyCommand.html @@ -0,0 +1,42 @@ + + + + + + + +
+ + + +
+
+ +ZincrbyCommand: Contents
  ZINCRBY _key_ _increment_ _member_ (Redis >
    Return value +
+ +

ZincrbyCommand

+ +
+ +
+ +
+ #sidebar SortedSetCommandsSidebar

ZINCRBY _key_ _increment_ _member_ (Redis >

1.1) = +Time complexity O(log(N)) with N being the number of elements in the sorted set
If member already exists in the sorted set adds the increment to its scoreand updates the position of the element in the sorted set accordingly.If member does not already exist in the sorted set it is added with_increment_ as score (that is, like if the previous score was virtually zero).If key does not exist a new sorted set with the specified_member_ as sole member is crated. If the key exists but does not hold asorted set value an error is returned.
+
The score value can be the string representation of a double precision floatingpoint number. It's possible to provide a negative value to perform a decrement.
+
For an introduction to sorted sets check the Introduction to Redis data types page.
+

Return value

Integer reply, specifically:

+The score of the member after the increment is performed.
+
+
+ +
+
+ + +