Description
On cluster connections, all connectionIds share a single GlideClusterClient. If a user runs SELECT <N> via Send Command, it changes the active database on the shared connection, affecting all other users/connections using that cluster client.
Possible Fix
Add SELECT to the command confirm list for cluster connections, since database selection should only happen at connection time via the databaseId client option.
Description
On cluster connections, all connectionIds share a single
GlideClusterClient. If a user runsSELECT <N>via Send Command, it changes the active database on the shared connection, affecting all other users/connections using that cluster client.Possible Fix
Add
SELECTto the command confirm list for cluster connections, since database selection should only happen at connection time via thedatabaseIdclient option.