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 | App - Schema Browser |
| Version | 08.0 |
Add to Server Registration->Advanced->[Object Folder] an option called "Use Schema Folder Grouping" with possible options of {Default, Yes, No}
In the XXDatabaseNode.java objects, have a condition to list XXXSchemaNode.java instead of the ObjectTableFolders.
This applies to a subset of servers/vendors. It applies to all vendors that have database. eg: MS SQL Server, Sybase ASE, Sybase Anywhere, Sybase IQ, Informix, nCluster, PostgreSQL.
Turns our we want a list of schema under the database node.
Turns our we want a list of schema under the database node.
Implemented preliminary code. I can see two issues:
1. ConnectionProperties.getCurrentSchema() seems to return a String[1] always, even when there are multiple schemas. (Sql Server 2000, Northwind)
2. The list of underlying objects (tables, etc.) must be filtered for a particular schema.
Implemented preliminary code. I can see two issues:
1. ConnectionProperties.getCurrentSchema() seems to return a String[1] always, even when there are multiple schemas. (Sql Server 2000, Northwind)
2. The list of underlying objects (tables, etc.) must be filtered for a particular schema.
Please see MsDatabaseNode.java line 77. This is the correct code we need to use on all the database nodes.
ArrayList schemaList = ConnectionMetaData.getSchemas(_properties, _conn, getDatabase());
Please see MsDatabaseNode.java line 77. This is the correct code we need to use on all the database nodes.
ArrayList schemaList = ConnectionMetaData.getSchemas(_properties, _conn, getDatabase());
-- GUI Support --
Derby: No
DB2 LUW: No
DB2 iSeries: No
DB2 z/OS: No
Informix: Yes
Oracle: No
MySQL: No
MS SQL Server 7/2k: Yes
MS SQL Server 25k/28k: Yes
Sybase ASE: Yes
Sybase Any: Yes
Sybase IQ: Yes
PostgreSQL: Yes
Teradata: No
nCluster: Yes
-- GUI Support --
Derby: No
DB2 LUW: No
DB2 iSeries: No
DB2 z/OS: No
Informix: Yes
Oracle: No
MySQL: No
MS SQL Server 7/2k: Yes
MS SQL Server 25k/28k: Yes
Sybase ASE: Yes
Sybase Any: Yes
Sybase IQ: Yes
PostgreSQL: Yes
Teradata: No
nCluster: Yes
extraction code for displaying nodes via schema is done needs testing some thought...
extraction code for displaying nodes via schema is done needs testing some thought...
need to change the detailed view extraction code to reflect schemas...
need to change the detailed view extraction code to reflect schemas...
ok tree nodes and detail data now displaying the correct data... needs testing
this is for:
(0) Informix
(1) nCluster
(2) PostgreSQL
(3) SQLServer
(4) Sybase ASE
(5) Sybase Anywhere
(6) Sybase IQ
ok tree nodes and detail data now displaying the correct data... needs testing
this is for:
(0) Informix
(1) nCluster
(2) PostgreSQL
(3) SQLServer
(4) Sybase ASE
(5) Sybase Anywhere
(6) Sybase IQ
Issue #2742 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
1 issue link |
relates to #14662
Issue #14662PostgreSQL -> Multi Select and Delete Schemas does not refresh the Tree Node |
This applies to a subset of servers/vendors. It applies to all vendors that have database. eg: MS SQL Server, Sybase ASE, Sybase Anywhere, Sybase IQ, Informix, nCluster, PostgreSQL.