- 17 Nov, 2015 5 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Maybe there are legitimate use cases for MIGRATE inside Lua scripts, at least for now. When the command will be executed in an asynchronous fashion (planned) it is possible we'll no longer be able to permit it from within Lua scripts.
-
antirez authored
Thanks to Oran Agra (@oranagra) for reporting. Key extraction would not work otherwise and it does not make sense to take wrong data in the command table.
-
- 10 Nov, 2015 1 commit
-
-
antirez authored
-
- 09 Nov, 2015 2 commits
- 05 Nov, 2015 1 commit
-
-
antirez authored
-
- 30 Oct, 2015 6 commits
-
-
antirez authored
Currently this feature is only accessible via DEBUG for testing, since otherwise depending on the instance configuration a given script works or is broken, which is against the Redis philosophy.
-
antirez authored
This commit also inverts two stanzas of the code just becuase they are more logical like that, not because currently it makes any difference.
-
antirez authored
-
antirez authored
By calling redis.replicate_commands(), the scripting engine of Redis switches to commands replication instead of replicating whole scripts. This is useful when the script execution is costly but only results in a few writes performed to the dataset. Morover, in this mode, it is possible to call functions with side effects freely, since the script execution does not need to be deterministic: anyway we'll capture the outcome from the point of view of changes to the dataset. In this mode math.random() returns different sequences at every call. If redis.replicate_commnads() is not called before any other write, the command returns false and sticks to whole scripts replication instead.
-
antirez authored
-
antirez authored
-
- 13 Oct, 2015 2 commits
- 02 Oct, 2015 1 commit
-
-
antirez authored
-
- 01 Oct, 2015 9 commits
- 30 Sep, 2015 2 commits
- 29 Jul, 2015 1 commit
-
-
antirez authored
-
- 28 Jul, 2015 5 commits
- 27 Jul, 2015 2 commits
- 26 Jul, 2015 3 commits