Database Browser | Alter User with multiple connected sessions causes wrong database to be updated. (4226413)

The wrong database is updated when altering a user. This only occurs in the situation in which there are 2 different connections opened and only one window open, specifically  one Schema Browser.

1. Open connection 1

2. Open connection 2

3. For connection 2 open the Schema Browser. No other windows open for either connection.

4. In that Schema Browser, select Users to list all users for connection 2.

5. Now change focus by clicking onto connection 1. At this point, Toad's live connection is to connection 1. But the live window is still on the schema browser based on connection 2 (connection 2's objects).

6. In the schema browser window, right click and select "alter user". A pop-up window opens to alter this particular user. It's available for a user that is in connection 2 (and may or may not exist in connection 1). But the window itself is accessiong connection 1's database.

This is problematic. If changes are made and applied, Toad will try to apply the changes to connection 1 incorrectly. If the user is not defined in connection 1's database, then it will error out that no user exist. But if a users with the same name happens to exist in connection 1's database thent he changes will be applied. Changes tthat may not be intended for that database.