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/keys.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 '')
-rw-r--r-- | iredis/data/commands/keys.md | 27 |
1 files changed, 15 insertions, 12 deletions
diff --git a/iredis/data/commands/keys.md b/iredis/data/commands/keys.md index 8991beb..186caca 100644 --- a/iredis/data/commands/keys.md +++ b/iredis/data/commands/keys.md @@ -1,25 +1,28 @@ Returns all keys matching `pattern`. While the time complexity for this operation is O(N), the constant times are -fairly low. For example, Redis running on an entry level laptop can scan a 1 -million key database in 40 milliseconds. +fairly low. +For example, Redis running on an entry level laptop can scan a 1 million key +database in 40 milliseconds. **Warning**: consider `KEYS` as a command that should only be used in production -environments with extreme care. It may ruin performance when it is executed -against large databases. This command is intended for debugging and special -operations, such as changing your keyspace layout. Don't use `KEYS` in your -regular application code. If you're looking for a way to find keys in a subset -of your keyspace, consider using `SCAN` or [sets][tdts]. +environments with extreme care. +It may ruin performance when it is executed against large databases. +This command is intended for debugging and special operations, such as changing +your keyspace layout. +Don't use `KEYS` in your regular application code. +If you're looking for a way to find keys in a subset of your keyspace, consider +using `SCAN` or [sets][tdts]. [tdts]: /topics/data-types#sets Supported glob-style patterns: -- `h?llo` matches `hello`, `hallo` and `hxllo` -- `h*llo` matches `hllo` and `heeeello` -- `h[ae]llo` matches `hello` and `hallo,` but not `hillo` -- `h[^e]llo` matches `hallo`, `hbllo`, ... but not `hello` -- `h[a-b]llo` matches `hallo` and `hbllo` +* `h?llo` matches `hello`, `hallo` and `hxllo` +* `h*llo` matches `hllo` and `heeeello` +* `h[ae]llo` matches `hello` and `hallo,` but not `hillo` +* `h[^e]llo` matches `hallo`, `hbllo`, ... but not `hello` +* `h[a-b]llo` matches `hallo` and `hbllo` Use `\` to escape special characters if you want to match them verbatim. |