- 10 Feb, 2015 3 commits
- 02 Feb, 2015 1 commit
-
-
mattcollier authored
Code was adding '\n' (line 521) to the end of NIL values exlusively making csv output inconsistent. Removed '\n'
-
- 09 Dec, 2014 1 commit
-
-
Jan-Erik Rediger authored
This allows shell pipes to correctly end redis-cli. Ref #2066
-
- 25 Nov, 2014 1 commit
-
-
antirez authored
-
- 30 Oct, 2014 1 commit
-
-
Matt Stancliff authored
Closes #2066
-
- 29 Oct, 2014 1 commit
-
-
antirez authored
-
- 27 Aug, 2014 9 commits
-
-
Dov Murik authored
Fix redis-cli prompt to state "not connected" after a SHUTDOWN command is sent.
-
antirez authored
-
charsyam authored
Closes #1129
-
cubicdaiya authored
According to the C standard, it is desirable to give the type 'void' to functions have no argument. Closes #1631
-
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
-
Jan-Erik Rediger authored
(Cleaned up a little by @mattsta) Closes #1774
-
Matt Stancliff authored
Some people need formatted output even when they have no interactive tty. Fixes #760
-
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
-
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
-
- 09 Jul, 2014 2 commits
- 26 Jun, 2014 1 commit
-
-
antirez authored
-
- 18 Jun, 2014 1 commit
-
-
Alex Suraci authored
-
- 17 Jun, 2014 1 commit
-
-
Matt Stancliff authored
If we run a long latency session and want to Ctrl-C out of it, it's nice to still get the summary output at the end.
-
- 06 Jun, 2014 1 commit
-
-
Andy Grunwald authored
-
- 13 Mar, 2014 1 commit
-
-
antirez authored
-
- 05 Mar, 2014 1 commit
-
-
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
-
- 25 Feb, 2014 7 commits
-
-
antirez authored
-
antirez authored
The computation is just something to take the CPU busy, no need to use a specific type. Since stdint.h was not included this prevented compilation on certain systems.
-
antirez authored
-
antirez authored
-
antirez authored
-
michael-grunder authored
This commit changes the findBigKeys() function in redis-cli.c to use the new SCAN command for iterating the keyspace, rather than RANDOMKEY. Because we can know when we're done using SCAN, it will exit after exhausting the keyspace.
-
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.
-
- 22 Jan, 2014 2 commits
- 26 Sep, 2013 1 commit
-
-
Michel Martens authored
-
- 04 Sep, 2013 1 commit
-
-
antirez authored
The code freed a reply object that was never created, resulting in a segfault every time randomkey returned a key that was deleted before we queried it for size.
-
- 12 Jul, 2013 1 commit
-
-
Jan-Erik Rediger authored
-
- 03 Jul, 2013 2 commits
-
-
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.
-
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.
-
- 11 Apr, 2013 1 commit
-
-
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
-