summaryrefslogtreecommitdiffstats
path: root/iredis/data/commands/select.md
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2023-01-04 07:19:32 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2023-01-04 07:19:32 +0000
commit7480e618ec785ba8a1c74c8a150cffe5880fb3bb (patch)
tree87422376dd9a7eee55850f0fce9a8bb4c13e44a2 /iredis/data/commands/select.md
parentAdding upstream version 1.12.1. (diff)
downloadiredis-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/select.md')
-rw-r--r--iredis/data/commands/select.md21
1 files changed, 4 insertions, 17 deletions
diff --git a/iredis/data/commands/select.md b/iredis/data/commands/select.md
index ff366c6..9ebc04e 100644
--- a/iredis/data/commands/select.md
+++ b/iredis/data/commands/select.md
@@ -1,26 +1,13 @@
Select the Redis logical database having the specified zero-based numeric index.
New connections always use the database 0.
-Selectable Redis databases are a form of namespacing: all databases are still
-persisted in the same RDB / AOF file. However different databases can have keys
-with the same name, and commands like `FLUSHDB`, `SWAPDB` or `RANDOMKEY` work on
-specific databases.
+Selectable Redis databases are a form of namespacing: all databases are still persisted in the same RDB / AOF file. However different databases can have keys with the same name, and commands like `FLUSHDB`, `SWAPDB` or `RANDOMKEY` work on specific databases.
-In practical terms, Redis databases should be used to separate different keys
-belonging to the same application (if needed), and not to use a single Redis
-instance for multiple unrelated applications.
+In practical terms, Redis databases should be used to separate different keys belonging to the same application (if needed), and not to use a single Redis instance for multiple unrelated applications.
-When using Redis Cluster, the `SELECT` command cannot be used, since Redis
-Cluster only supports database zero. In the case of a Redis Cluster, having
-multiple databases would be useless and an unnecessary source of complexity.
-Commands operating atomically on a single database would not be possible with
-the Redis Cluster design and goals.
+When using Redis Cluster, the `SELECT` command cannot be used, since Redis Cluster only supports database zero. In the case of a Redis Cluster, having multiple databases would be useless and an unnecessary source of complexity. Commands operating atomically on a single database would not be possible with the Redis Cluster design and goals.
-Since the currently selected database is a property of the connection, clients
-should track the currently selected database and re-select it on reconnection.
-While there is no command in order to query the selected database in the current
-connection, the `CLIENT LIST` output shows, for each client, the currently
-selected database.
+Since the currently selected database is a property of the connection, clients should track the currently selected database and re-select it on reconnection. While there is no command in order to query the selected database in the current connection, the `CLIENT LIST` output shows, for each client, the currently selected database.
@return