diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-04 07:19:32 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2023-01-04 07:19:32 +0000 |
commit | 7480e618ec785ba8a1c74c8a150cffe5880fb3bb (patch) | |
tree | 87422376dd9a7eee55850f0fce9a8bb4c13e44a2 /iredis/data/commands/rename.md | |
parent | Adding upstream version 1.12.1. (diff) | |
download | iredis-7480e618ec785ba8a1c74c8a150cffe5880fb3bb.tar.xz iredis-7480e618ec785ba8a1c74c8a150cffe5880fb3bb.zip |
Adding upstream version 1.13.0.upstream/1.13.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'iredis/data/commands/rename.md')
-rw-r--r-- | iredis/data/commands/rename.md | 21 |
1 files changed, 8 insertions, 13 deletions
diff --git a/iredis/data/commands/rename.md b/iredis/data/commands/rename.md index 5a38f63..471ecf4 100644 --- a/iredis/data/commands/rename.md +++ b/iredis/data/commands/rename.md @@ -1,17 +1,8 @@ -Renames `key` to `newkey`. It returns an error when `key` does not exist. If -`newkey` already exists it is overwritten, when this happens `RENAME` executes -an implicit `DEL` operation, so if the deleted key contains a very big value it -may cause high latency even if `RENAME` itself is usually a constant-time -operation. +Renames `key` to `newkey`. +It returns an error when `key` does not exist. +If `newkey` already exists it is overwritten, when this happens `RENAME` executes an implicit `DEL` operation, so if the deleted key contains a very big value it may cause high latency even if `RENAME` itself is usually a constant-time operation. -In Cluster mode, both `key` and `newkey` must be in the same **hash slot**, -meaning that in practice only keys that have the same hash tag can be reliably -renamed in cluster. - -@history - -- `<= 3.2.0`: Before Redis 3.2.0, an error is returned if source and destination - names are the same. +In Cluster mode, both `key` and `newkey` must be in the same **hash slot**, meaning that in practice only keys that have the same hash tag can be reliably renamed in cluster. @return @@ -24,3 +15,7 @@ SET mykey "Hello" RENAME mykey myotherkey GET myotherkey ``` + +## Behavior change history + +* `>= 3.2.0`: The command no longer returns an error when source and destination names are the same.
\ No newline at end of file |