Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
If you open ADS and ADS restores the Workspace of Query Windows, each Query Window is opened synchronously, but the connection establishment are done asynchronously. If there are multiple Query Windows connected to the same database and the password has changed, you will have multiple attempts with the wrong password and the database may lock your account.
We need an option to either prevent the establishing of connections when restoring the workspace, or and option to allow the user to restore one query window at a time with user confirmation.
|
|
65 KB
|
|
63 KB
|
|
66 KB
|
|
153 KB
The following have been implemented:
1. Added a new boolean option in File > Options > General > Workspace > Establish database connection during workspace restore. Default value is true.
2. When ADS starts and the above option is set to false, previously opened Query Analyzer, FluidShell and MongoShell tabs will not connect to their respective servers. Instead, a message is displayed to the user (see attached screenshots). However, if the server registration of these tabs does not enable password save, then this message is not shown to the user (instead the authenticate panel is displayed).
3. Added Query > Disconnect All Windows and Query > Reconnect All Windows menu items. These actions disconnect or reconnect all currently opened Query Analyzer, FluidShell and MongoShell tabs.
4. If a query window is currently executing a query and the user initiates a Disconnect All Windows or a Reconnect All Windows action, then nothing should happen until the current execution is finished (during execution, the toolbar's Disconnect and Reconnect icons are disabled). No disconnect/reconnect requests are queued.
@kin-hong:
1) In the Query menu, lets put Reconnect All Windows first & then Disconnect All Windows
2) In a QA window, lets modify the "To establish a connection, use the Query > Reconnect All Windows menu command to:
To establish a connection, use either the Query > Reconnect All Windows menu command or click the Reconnect button
Once done w/ this these & Tariq's reported issue, pls back port to v18 & mark issue as resolved
@kin-hong:
1) In the Query menu, lets put Reconnect All Windows first & then Disconnect All Windows
2) In a QA window, lets modify the "To establish a connection, use the Query > Reconnect All Windows menu command to:
To establish a connection, use either the Query > Reconnect All Windows menu command or click the Reconnect button
Once done w/ this these & Tariq's reported issue, pls back port to v18 & mark issue as resolved
QA found a regression problem, VA:#9540. I've fixed it in both v18 and v19.
QA found a regression problem, VA:#9540. I've fixed it in both v18 and v19.
Verified all items in ADS v18.0.13-6 and 19.0.0-alpha-21
Verified all items in ADS v18.0.13-6 and 19.0.0-alpha-21
Issue #15256 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 18.0.13-6, 19.0.0-alpha-20 |
| No time estimate |
1 issue link |
relates to #14806
Issue #14806Cannot retry failed connection once password changes |
The following have been implemented:
1. Added a new boolean option in File > Options > General > Workspace > Establish database connection during workspace restore. Default value is true.
2. When ADS starts and the above option is set to false, previously opened Query Analyzer, FluidShell and MongoShell tabs will not connect to their respective servers. Instead, a message is displayed to the user (see attached screenshots). However, if the server registration of these tabs does not enable password save, then this message is not shown to the user (instead the authenticate panel is displayed).
3. Added Query > Disconnect All Windows and Query > Reconnect All Windows menu items. These actions disconnect or reconnect all currently opened Query Analyzer, FluidShell and MongoShell tabs.
4. If a query window is currently executing a query and the user initiates a Disconnect All Windows or a Reconnect All Windows action, then nothing should happen until the current execution is finished (during execution, the toolbar's Disconnect and Reconnect icons are disabled). No disconnect/reconnect requests are queued.