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
While working on issue #938, I did not modify Enable/Disable Trigger related code.
https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/938
Option to have the Visual Editing dialogs be modeless dialogs with new connections
Enable/Disable Trigger dialog currently is displayed as a tab. Niels asked me log this issue so that he can review the behavior of these two dialogs later on.
These dialogs are all derived from the ExecuteStatementDialog class which prompts a question and asks for a confirmation. There are 20+ dialogs that are all derived from the ExecuteStatementDialog class. The Start/Stop/Enable/Disable Job dialogs described in issue #7284 are derived from the ExecuteStatementDialog class as well. I have marked #7284 a duplicate of this issue.
We now have CommonSchemaTab and CommonSchemaDialog. I think the ExecuteStatementDialog should extend CommonSchemaDialog instead of CommonSchemaTab.
We now have CommonSchemaTab and CommonSchemaDialog. I think the ExecuteStatementDialog should extend CommonSchemaDialog instead of CommonSchemaTab.
The following classes are derived from the ExecuteStatementDialog:
CoalesceTablespaceDialog, DisconnectSessionDialog, EnableTriggerDialog, FlushSGADialog, KillSessionDialog,
MssqlCheckpointDialog, MssqlDisableJobDialog, MssqlEnableJobDialog, MssqlSetOnlineDialog, MssqlStartJobDialog,
MssqlStopJobDialog, MssqlUpdateStatisticsDialog, OraDisableJobDialog, OraEnableJobDialog, OraStartJobDialog,
OraStopJobDialog, StartTraceDialog, StopTraceDialog, SwitchLogFileDialog, SybaseCheckpointDialog,
SybaseReinitDatabaseDeviceDialog, SybaseSetOnlineDialog, TakeCheckpointDialog, UnpinCodeDialog
This means I need to find callers of all of classes listed above and revert change made by Andy in early March. In addition, database operations might be needed before display the modal dialog, those database operations will be executed in EDT.
The following classes are derived from the ExecuteStatementDialog:
CoalesceTablespaceDialog, DisconnectSessionDialog, EnableTriggerDialog, FlushSGADialog, KillSessionDialog,
MssqlCheckpointDialog, MssqlDisableJobDialog, MssqlEnableJobDialog, MssqlSetOnlineDialog, MssqlStartJobDialog,
MssqlStopJobDialog, MssqlUpdateStatisticsDialog, OraDisableJobDialog, OraEnableJobDialog, OraStartJobDialog,
OraStopJobDialog, StartTraceDialog, StopTraceDialog, SwitchLogFileDialog, SybaseCheckpointDialog,
SybaseReinitDatabaseDeviceDialog, SybaseSetOnlineDialog, TakeCheckpointDialog, UnpinCodeDialog
This means I need to find callers of all of classes listed above and revert change made by Andy in early March. In addition, database operations might be needed before display the modal dialog, those database operations will be executed in EDT.
All of these dialogs are displayed as a modal dialog now.
CoalesceTablespaceDialog - Oracle Storage Manager
DisconnectSessionDialog - Session Manager
EnableTriggerDialog - schema tree Trigger node
FlushSGADialog - SGA Manager
KillSessionDialog - Session Manager
MssqlCheckpointDialog - Mssql Storage Manager
MssqlDisableJobDialog - schema tree Job node and Server Agent
MssqlEnableJobDialog - schema tree Job node and Server Agent
MssqlSetOnlineDialog - Mssql Storage Manager
MssqlStartJobDialog - schema tree Job node and Server Agent
MssqlStopJobDialog - schema tree Job node and Server Agent
MssqlUpdateStatisticsDialog - Mssql Storage Manager
OraDisableJobDialog - Oracle Instance Manager
OraEnableJobDialog - Oracle Instance Manager
OraStartJobDialog - Oracle Instance Manager
OraStopJobDialog - Oracle Instance Manager
StartTraceDialog - Session Manager
StopTraceDialog - Session Manager
SwitchLogFileDialog - Log Manager
SybaseCheckpointDialog - Sybase Storage Manager
SybaseReinitDatabaseDeviceDialog - Sybase Storage Manager
SybaseSetOnlineDialog - Sybase Storage Manager
TakeCheckpointDialog - Log Manager
UnpinCodeDialog - SGA Manager
All of these dialogs are displayed as a modal dialog now.
CoalesceTablespaceDialog - Oracle Storage Manager
DisconnectSessionDialog - Session Manager
EnableTriggerDialog - schema tree Trigger node
FlushSGADialog - SGA Manager
KillSessionDialog - Session Manager
MssqlCheckpointDialog - Mssql Storage Manager
MssqlDisableJobDialog - schema tree Job node and Server Agent
MssqlEnableJobDialog - schema tree Job node and Server Agent
MssqlSetOnlineDialog - Mssql Storage Manager
MssqlStartJobDialog - schema tree Job node and Server Agent
MssqlStopJobDialog - schema tree Job node and Server Agent
MssqlUpdateStatisticsDialog - Mssql Storage Manager
OraDisableJobDialog - Oracle Instance Manager
OraEnableJobDialog - Oracle Instance Manager
OraStartJobDialog - Oracle Instance Manager
OraStopJobDialog - Oracle Instance Manager
StartTraceDialog - Session Manager
StopTraceDialog - Session Manager
SwitchLogFileDialog - Log Manager
SybaseCheckpointDialog - Sybase Storage Manager
SybaseReinitDatabaseDeviceDialog - Sybase Storage Manager
SybaseSetOnlineDialog - Sybase Storage Manager
TakeCheckpointDialog - Log Manager
UnpinCodeDialog - SGA Manager
Issue #7268 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build trunk/28633 |
| No time estimate |
These dialogs are all derived from the ExecuteStatementDialog class which prompts a question and asks for a confirmation. There are 20+ dialogs that are all derived from the ExecuteStatementDialog class. The Start/Stop/Enable/Disable Job dialogs described in issue #7284 are derived from the ExecuteStatementDialog class as well. I have marked #7284 a duplicate of this issue.