1. 12 Nov, 2014 1 commit
  2. 29 Oct, 2014 5 commits
  3. 06 Oct, 2014 2 commits
  4. 19 Sep, 2014 1 commit
  5. 17 Sep, 2014 1 commit
    • antirez's avatar
      Don't propagate SAVE. · ef61ab63
      antirez authored
      This is a general fix (check that dirty delta is positive) but actually
      should have as the only effect fixing the SAVE propagation to
      AOF and slaves.
      ef61ab63
  6. 08 Sep, 2014 1 commit
  7. 26 Aug, 2014 9 commits
  8. 28 Jul, 2014 1 commit
  9. 18 Jul, 2014 10 commits
  10. 27 Jun, 2014 6 commits
    • antirez's avatar
      DEBUG CMDKEYS moved to COMMAND GETKEYS. · b18c92b9
      antirez authored
      b18c92b9
    • antirez's avatar
      COMMAND COUNT subcommand added. · d3f43db2
      antirez authored
      d3f43db2
    • antirez's avatar
      COMMAND: fix argument parsing. · b2051198
      antirez authored
      This fixes detection of wrong subcommand (that resulted in the default
      all-commands output instead) and allows COMMAND INFO to be called
      without arguments (resulting into an empty array) which is useful in
      programmtically generated calls like the following (in Ruby):
      
          redis.commands("command","info",*mycommands)
      
      Note: mycommands may be empty.
      b2051198
    • antirez's avatar
      COMMANDS command renamed COMMAND. · 3364b2d1
      antirez authored
      3364b2d1
    • antirez's avatar
      COMMANDS command: remove static + aesthetic changes. · 0aab8eb1
      antirez authored
      Static was removed since it is needed in order to get symbols in stack
      traces. Minor changes in the source code were operated to make it more
      similar to the existing Redis code base.
      0aab8eb1
    • Matt Stancliff's avatar
      Cluster: Add COMMANDS command · 60d62a99
      Matt Stancliff authored
      COMMANDS returns a nested multibulk reply for each
      command in the command table.  The reply for each
      command contains:
        - command name
        - arity
        - array of command flags
        - start key position
        - end key position
        - key offset step
        - optional: if the keys are not deterministic and
          Redis uses an internal key evaluation function,
          the 6th field appears and is defined as a status
          reply of: REQUIRES ARGUMENT PARSING
      
      Cluster clients need to know where the keys are in each
      command to implement proper routing to cluster nodes.
      
      Redis commands can have multiple keys, keys at offset steps, or other
      issues where you can't always assume the first element after
      the command name is the cluster routing key.
      
      Using the information exposed by COMMANDS, client implementations
      can have live, accurate key extraction details for all commands.
      
      Also implements COMMANDS INFO [commands...] to return only a
      specific set of commands instead of all 160+ commands live in Redis.
      60d62a99
  11. 26 Jun, 2014 1 commit
  12. 23 Jun, 2014 1 commit
  13. 21 Jun, 2014 1 commit