1. 08 Dec, 2014 1 commit
  2. 25 Nov, 2014 1 commit
  3. 11 Nov, 2014 1 commit
  4. 30 Oct, 2014 1 commit
  5. 29 Oct, 2014 1 commit
  6. 27 Oct, 2014 1 commit
  7. 15 Oct, 2014 1 commit
  8. 18 Aug, 2014 1 commit
  9. 13 Aug, 2014 1 commit
  10. 08 Aug, 2014 2 commits
  11. 07 Aug, 2014 5 commits
    • Kashif Rasul's avatar
      Fix issues raised by clang analyzer · c49378fe
      Kashif Rasul authored
      Modified by @antirez since the original fix to genInfoString() looked
      weak. Probably the clang analyzer complained about `section` being
      possibly NULL, and strcasecmp() called with a NULL pointer. In the
      practice this can never happen, still for the sake of correctness
      the right fix is not to modify only the first call, but to set `section`
      to the value of "default" if it happens to be NULL.
      
      Closes #1660
      c49378fe
    • Jan-Erik Rediger's avatar
      redis-cli: fix latency result output · 05676c5d
      Jan-Erik Rediger authored
      (Cleaned up a little by @mattsta)
      
      Closes #1774
      05676c5d
    • Matt Stancliff's avatar
      redis-cli: Add --no-raw option · 42655316
      Matt Stancliff authored
      Some people need formatted output even when they have no
      interactive tty.
      
      Fixes #760
      42655316
    • Matt Stancliff's avatar
      redis-cli: stop showing incorrectly selected DB · 0042fb0e
      Matt Stancliff authored
      Previously redis-cli would happily show "-1" or "99999"
      as valid DB choices.
      
      Now, if the SELECT call returned an error, we don't update
      the DB number in the CLI.
      
      Inspired by @anupshendkar in #1313
      
      Fixes #566, #1313
      0042fb0e
    • Matt Stancliff's avatar
      redis-cli: Re-attach selected DB after auth · bbc1cd0b
      Matt Stancliff authored
      Previously, if you did SELECT then AUTH, redis-cli
      would show your SELECT'd db even though it didn't
      happen.
      
      Note: running into this situation is a (hopefully) very limited
      used case of people using multiple DBs and AUTH all at the same
      time.
      
      Fixes antirez#1639
      bbc1cd0b
  12. 08 Jul, 2014 1 commit
  13. 02 Jul, 2014 1 commit
  14. 26 Jun, 2014 1 commit
  15. 18 Jun, 2014 1 commit
  16. 17 Jun, 2014 1 commit
  17. 22 May, 2014 1 commit
  18. 13 Mar, 2014 1 commit
  19. 27 Feb, 2014 1 commit
    • michael-grunder's avatar
      Improved bigkeys with progress, pipelining and summary · 806788d0
      michael-grunder authored
      This commit reworks the redis-cli --bigkeys command to provide more
      information about our progress as well as output summary information
      when we're done.
      
       - We now show an approximate percentage completion as we go
       - Hiredis pipelining is used for TYPE and SIZE retreival
       - A summary of keyspace distribution and overall breakout at the end
      806788d0
  20. 25 Feb, 2014 6 commits
  21. 10 Feb, 2014 1 commit
    • Matt Stancliff's avatar
      Auto-enter slaveMode when SYNC from redis-cli · 21648473
      Matt Stancliff authored
      If someone asks for SYNC or PSYNC from redis-cli,
      automatically enter slaveMode (as if they ran
      redis-cli --slave) and continue printing the replication
      stream until either they Ctrl-C or the master gets disconnected.
      21648473
  22. 22 Jan, 2014 2 commits
  23. 26 Sep, 2013 1 commit
  24. 04 Sep, 2013 1 commit
  25. 11 Jul, 2013 1 commit
  26. 03 Jul, 2013 2 commits
    • antirez's avatar
      redis-cli: introduced --pipe-timeout. · 1135e9fa
      antirez authored
      When in --pipe mode, after all the data transfer to the server is
      complete, now redis-cli waits at max the specified amount of
      seconds (30 by default, use 0 to wait forever) without receiving any
      reply at all from the server. After this time limit the operation is
      aborted with an error.
      
      That's related to issue #681.
      1135e9fa
    • antirez's avatar
      redis-cli --pipe: send final ECHO in a safer way. · fbb97c6b
      antirez authored
      If the protocol read from stdin happened to contain grabage (invalid
      random chars), in the previous implementation it was possible to end
      with something like:
      
      dksfjdksjflskfjl*2\r\n$4\r\nECHO....
      
      That is invalid as the *2 should start into a new line. Now we prefix
      the ECHO with a CRLF that has no effects on the server but prevents this
      issues most of the times.
      
      Of course if the offending wrong sequence is something like:
      
      $3248772349\r\n
      
      No one is going to save us as Redis will wait for data in the context of
      a big argument, so this fix does not cover all the cases.
      
      This partially fixes issue #681.
      fbb97c6b
  27. 11 Apr, 2013 2 commits
    • antirez's avatar
      redis-cli: raise error on bad command line switch. · f8ae70cf
      antirez authored
      Previously redis-cli never tried to raise an error when an unrecognized
      switch was encountered, as everything after the initial options is to be
      transmitted to the server.
      
      However this is too liberal, as there are no commands starting with "-".
      So the new behavior is to produce an error if there is an unrecognized
      switch starting with "-". This should not break past redis-cli usages
      but should prevent broken options to be silently discarded.
      
      As far the first token not starting with "-" is encountered, all the
      rest is considered to be part of the command, so you cna still use
      strings starting with "-" as values, like in:
      
          redis-cli --port 6380 set foo --my-value
      f8ae70cf
    • antirez's avatar
      redis-cli: --latency-history mode implemented. · 0280c2f2
      antirez authored
      0280c2f2