X-Git-Url: https://git.saurik.com/redis.git/blobdiff_plain/b882056c93f3e3afe5fde9d62fb569ce30a76a76..d021221086c9a6c5af404f3017791605b70c592d:/doc/IntroductionToRedisDataTypes.html
diff --git a/doc/IntroductionToRedisDataTypes.html b/doc/IntroductionToRedisDataTypes.html
index 26b2ba19..82078aeb 100644
--- a/doc/IntroductionToRedisDataTypes.html
+++ b/doc/IntroductionToRedisDataTypes.html
@@ -79,7 +79,7 @@ $ ./redis-cli sismember myset 3
(integer) 1
$ ./redis-cli sismember myset 30
(integer) 0
-"3" is a member of the set, while "30" is not. Sets are very good in order to express relations between objects. For instance we can easily Redis Sets in order to implement tags.
A simple way to model this is to have, for every object you want to tag, a Set with all the IDs of the tags associated with the object, and for every tag that exists, a Set of of all the objects tagged with this tag.
For instance if our news ID 1000 is tagged with tag 1,2,5 and 77, we can specify the following two Sets:
+"3" is a member of the set, while "30" is not. Sets are very good in order to express relations between objects. For instance we can easily use Redis Sets in order to implement tags.
$ ./redis-cli sadd news:1000:tags 1 (integer) 1 $ ./redis-cli sadd news:1000:tags 2 @@ -143,7 +143,6 @@ $ ./redis-cli zrangebyscore hackers -inf 1950 $ ./redis-cli zremrangebyscore hackers 1940 1960 (integer) 2ZREMRANGEBYSCORE is not the best command name, but it can be very useful, and returns the number of removed elements.