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 - General |
| Version | Future - .1 |
Version: 13.0-dev-53
Build #: 30529
Build Date: 2012-Dec-08 08:55:08 AM
Greenplum - Detail view doesnt follow the exact ordering as the Schema Tree Browser.
SInce the queries doesnt seem to be similar, I find it difficult to find the objects in the detail view when compared to Tree Browser for Greenplum
1. Tables
2. Sequences
3. Constraints
4. Sytem Functions
5. Operators
See attached pics
For the node Operators, the detail view seems to be repeating items.
For System Functions, I can see more objects in the Detail View than in the Tree Node
see latest attachment... for the Detail View to accurately match the Schema Browser, the Name column needs to be sorted by clicking its column header.
see latest attachment... for the Detail View to accurately match the Schema Browser, the Name column needs to be sorted by clicking its column header.
For the problems described in this issue, you likely can reproduce all of them on PostgreSQL servers too (same implementation); and perhaps in some of other supported servers as well.
The reason why objects are presented in different count/order in schema browser and detail view is they use different queries to retrieve objects. Tree node constructs its own SQL to retrieve objects, detail view uses backend Extract class to get objects; that's why number of objects and their order are presented differently.
I am not sure whether we want to fix this in 13.0 or not, reassigned to Sachin for decision.
For the problems described in this issue, you likely can reproduce all of them on PostgreSQL servers too (same implementation); and perhaps in some of other supported servers as well.
The reason why objects are presented in different count/order in schema browser and detail view is they use different queries to retrieve objects. Tree node constructs its own SQL to retrieve objects, detail view uses backend Extract class to get objects; that's why number of objects and their order are presented differently.
I am not sure whether we want to fix this in 13.0 or not, reassigned to Sachin for decision.
Issue #8048 |
| Closed |
Completion |
| No due date |
| No fixed build |
| No time estimate |
For the node Operators, the detail view seems to be repeating items.
For System Functions, I can see more objects in the Detail View than in the Tree Node