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
Aqua Data Studio 15.0.0-dev-68
Build #: 35490
Built on: 2014-Jan-09 03:08:18 PM
Operating System: Cent OS 6.4
Database version : voltdb-ent-3.7
Step 1: Connect to VoltDB.
Step 2: Expand tables node -> Right click on any existing table(say,Votes in my case) -> Open Query analyzer -> Write following query:
"SELECT FROM VOTES limit 10"
Step 3: Keep cursor between SELECT and FROM keywords -> Hit Control+Space
Auto-completion box "current table columns" for column list for selected table appears.
Here you will observe that column sequence in pop up window is not same as column sequence of selected table in tree node.(please refer voltdb.png)
Follow same steps for other database(say, Greenplum or PostgreSQL), column sequence in "Current table columns" pop up is same as column sequence shown in tree node for selected table.(please refer greenplum.png)
|
|
124 KB
|
|
139 KB
|
|
154 KB
I executed "Select * from votes limit 10" query on voted table.
Also right click on table "votes"-> Select option "Script object to window as" -> create.
Here i observed that order of columns in resultset of above executed query and column order in create script are same as order of columns in "Current table columns" window. (refer image.png)
Thus, column order is wrong in tree node not in "Current table column" window. In other databases, column order in tree node is same as they are created in table while in VoltDB column order is sorted alphabetically.
Nodes are normally sorted alphabetical except for column nodes. VoltDB has to extract this via the jdbc metadata method that doesn't allow for sorting by ordinal position. modified VoltDB column nodes to use a HashMap and sort by ordinal position in code. will affect table columns, view columns, index columns, constraint columns and procedure columns in the tree
Nodes are normally sorted alphabetical except for column nodes. VoltDB has to extract this via the jdbc metadata method that doesn't allow for sorting by ordinal position. modified VoltDB column nodes to use a HashMap and sort by ordinal position in code. will affect table columns, view columns, index columns, constraint columns and procedure columns in the tree
verified in ADS 15.0.0 dev-225 using VoltDB 4.0
verified in ADS 15.0.0 dev-225 using VoltDB 4.0
Issue #11348 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v15.0.0-dev-95 |
| No time estimate |
I executed "Select * from votes limit 10" query on voted table.
Also right click on table "votes"-> Select option "Script object to window as" -> create.
Here i observed that order of columns in resultset of above executed query and column order in create script are same as order of columns in "Current table columns" window. (refer image.png)
Thus, column order is wrong in tree node not in "Current table column" window. In other databases, column order in tree node is same as they are created in table while in VoltDB column order is sorted alphabetically.