1. 21 Nov, 2013 29 commits
  2. 11 Nov, 2013 1 commit
  3. 10 Nov, 2013 1 commit
  4. 07 Nov, 2013 1 commit
  5. 06 Nov, 2013 4 commits
  6. 05 Nov, 2013 4 commits
    • antirez's avatar
      Fixed typo in parseScanCursorOrReply(): ad -> at. · 3a66e0c1
      antirez authored
      Thanks to @badboy for reporting it.
      3a66e0c1
    • antirez's avatar
      SCAN code refactored to parse cursor first. · 060d56e7
      antirez authored
      The previous implementation of SCAN parsed the cursor in the generic
      function implementing SCAN, SSCAN, HSCAN and ZSCAN.
      
      The actual higher-level command implementation only checked for empty
      keys and return ASAP in that case. The result was that inverting the
      arguments of, for instance, SSCAN for example and write:
      
          SSCAN 0 key
      
      Instead of
      
          SSCAN key 0
      
      Resulted into no error, since 0 is a non-existing key name very likely.
      Just the iterator returned no elements at all.
      
      In order to fix this issue the code was refactored to extract the
      function to parse the cursor and return the error. Every higher level
      command implementation now parses the cursor and later checks if the key
      exist or not.
      060d56e7
    • antirez's avatar
      SCAN: when iterating ziplists or intsets always return cursor of 0. · 162acd8a
      antirez authored
      The previous implementation assumed that the first call always happens
      with cursor set to 0, this may not be the case, and we want to return 0
      anyway otherwise the (broken) client code will loop forever.
      162acd8a
    • antirez's avatar
      406be0ea