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
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | Q Analyzer |
| Version | Future - PM |
This is not a data studio issue. All databases work slightly different and DB2 allows for a user to set current_schema to a schema that do not exist. If you drop the schema that your query analyzer is assigned to from a different connection and try to reconnect the query analyzer it should attempt to connect back to the non existing schema and DB2 allows for this. The schema drop down will not get a schema assigned, so the first schema will be selected. If the user issues a query on a table without qualifying the object name with the schema it will return a sql exception stating the <schema>.<object> does not exist and the user is responsible for changing to the correct schema he wishes to use. This is DB2 behavior... Users could request a "Current Schema" Label if they need, in order to show not just the schema list but the current schema set, but this would be more of an enhancement and it has never been requested.
Issue #14234 |
| New |
Completion |
| No due date |
| No fixed build |
| No time estimate |
This is not a data studio issue. All databases work slightly different and DB2 allows for a user to set current_schema to a schema that do not exist. If you drop the schema that your query analyzer is assigned to from a different connection and try to reconnect the query analyzer it should attempt to connect back to the non existing schema and DB2 allows for this. The schema drop down will not get a schema assigned, so the first schema will be selected. If the user issues a query on a table without qualifying the object name with the schema it will return a sql exception stating the <schema>.<object> does not exist and the user is responsible for changing to the correct schema he wishes to use. This is DB2 behavior... Users could request a "Current Schema" Label if they need, in order to show not just the schema list but the current schema set, but this would be more of an enhancement and it has never been requested.