- 13 Dec, 2015 2 commits
- 23 May, 2014 1 commit
-
-
antirez authored
-
- 09 Jan, 2014 1 commit
-
-
antirez authored
-
- 14 Nov, 2012 2 commits
- 07 Nov, 2012 2 commits
-
-
antirez authored
With COPY now MIGRATE does not remove the key from the source instance. With REPLACE it uses RESTORE REPLACE on the target host so that even if the key already eixsts in the target instance it will be overwritten. The options can be used together.
-
antirez authored
The REPLACE option deletes an existing key with the same name (if any) and materializes the new one. The default behavior without RESTORE is to return an error if a key already exists.
-
- 02 Jun, 2012 1 commit
-
-
Alex Mitrofanov authored
(additional commit notes by antirez@gmail.com): The rdbIsObjectType() macro was not updated when the new RDB object type of ziplist encoded hashes was added. As a result RESTORE, that uses rdbLoadObjectType(), failed when a ziplist encoded hash was loaded. This does not affected normal RDB loading because in that case we use the lower-level function rdbLoadType(). The commit also adds a regression test.
-
- 03 Apr, 2012 1 commit
-
-
antirez authored
-
- 02 Apr, 2012 2 commits