|
136 KB
Field | Old Value | New Value |
---|---|---|
Description |
Aqua Data Studio 15.0.0-dev-66
Built on: 2014-Jan-07 02:23:17 PM
Database version : VoltDB-ent-3.7
1.Connect to VoltDB
In tree node expand VoltDB database Server
Select any Databases node,expand it
Select Table node,expand it
Select any two tables in my case I have selected "CONTESTANTS" and "AREA_CODE_STATE",expand it
Go to Column folder,expand it
Select any column
In my case I have selected "CONTESTANT_NUMBER","STATE","CONTESTANT_NUMBER" columns,drag and drop in Query Analyzer
with column names datatype is also appended,please see the screenshot
|
Aqua Data Studio 15.0.0-dev-66
Built on: 2014-Jan-07 02:23:17 PM
Database version : VoltDB-ent-3.7
1.Connect to VoltDB
In tree node expand VoltDB database Server
Select any Databases node,expand it
Select Table node,expand it
Select any two tables in my case I have selected "CONTESTANTS" and "AREA_CODE_STATE",expand it
Go to Column folder,expand it
Select any column
In my case I have selected "CONTESTANT_NUMBER","STATE","CONTESTANT_NUMBER" columns,
drag and drop in Query Analyzer with column names datatype of that column also display,please see the screenshot
|
Field | Old Value | New Value |
---|---|---|
Dev Assignee | JohnLH (John LH) | funfun (Fun Fun) |
@funfun: Instead of fixing this issue, can you specify what needs to be done so that all team members are aware of how to handle this correctly when a new DB is added.
Field | Old Value | New Value |
---|---|---|
Component | App - General | DB - VoltDB |
Dev Assignee | funfun (Fun Fun) | ivangron (Ivan Gron) |
>> @funfun: Instead of fixing this issue, can you specify what needs to be done so that all team members are aware of how to handle this correctly when a new DB is added.
It is explained in issue 11030 already:
"... Fix made by issue 6096 seems to add a 'public boolen isColumnNode()' API to the tree node, and, a DB column tree node supposes to redefine this method to return true. Since ADS column tree nodes do not share a common base column node class, hence, we need to modify each DB column tree node and add isColumnNode() manually. ..."
There are some other databases have this problem, not fixed yet. See issue 11030 for more info.
For VoltDB, simply add
@Override
public boolean isColumnNode() {
return true;
}
to VoltColumnNode.java should fix the problem. I don't have access to VoltDB, please email me a VoltDB server properties file if you want me to fix this issue.
>> @funfun: Instead of fixing this issue, can you specify what needs to be done so that all team members are aware of how to handle this correctly when a new DB is added.
It is explained in issue 11030 already:
"... Fix made by issue 6096 seems to add a 'public boolen isColumnNode()' API to the tree node, and, a DB column tree node supposes to redefine this method to return true. Since ADS column tree nodes do not share a common base column node class, hence, we need to modify each DB column tree node and add isColumnNode() manually. ..."
There are some other databases have this problem, not fixed yet. See issue 11030 for more info.
For VoltDB, simply add
@Override
public boolean isColumnNode() {
return true;
}
to VoltColumnNode.java should fix the problem. I don't have access to VoltDB, please email me a VoltDB server properties file if you want me to fix this issue.
Field | Old Value | New Value |
---|---|---|
Resolution | Fixed | |
Resolved Date | Feb 5, 2014 6:08 PM | |
Status | New | Resolved |
node method added and drag and drop is now working.
node method added and drag and drop is now working.
Field | Old Value | New Value |
---|---|---|
Fixed Build | v15.0.0-dev-95 |
Field | Old Value | New Value |
---|---|---|
Status | Resolved | Verified |
Field | Old Value | New Value |
---|---|---|
Status | Verified | Closed |
Issue #11329 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v15.0.0-dev-95 |
No time estimate |
1 issue link |
relates to #11030
Issue #11030Drag and Drop columns appends the datatype as well |
@funfun: Instead of fixing this issue, can you specify what needs to be done so that all team members are aware of how to handle this correctly when a new DB is added.