[
https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu...
]
Van Halbert commented on TEIIDDES-2256:
---------------------------------------
I like the new 3 column layout. But would it make sense to order them: runtime ->
Design time --> base type
and sort them by runtime.
Because the user is trying to match, based on what the runtime type is from the import, to
see all the options that are suggested to use based on that runtime type. By displaying
by design type, the user has to scroll thru all the runtime types to find all the
possibilities.
Confusing data type "integer" and "int"
---------------------------------------
Key: TEIIDDES-2256
URL:
https://issues.jboss.org/browse/TEIIDDES-2256
Project: Teiid Designer
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Import/Export
Affects Versions: 8.6
Reporter: Ramesh Reddy
Assignee: Paul Richardson
Fix For: 8.7, 8.6.1
Attachments: full-datatypes-1.png, full-datatypes-2.png, set-datatype-dialog.png,
set-datatype-dialog_2.png
I understand that
"integer" maps to "xs:biginteger"
"int" maps "xs:long"
How they are confusing when there is already one available for biginteger. Also the Table
creation wizard does not provide option to to select "int". When user chooses
"integer" it often is "int".
This confusion needs to be resolved. IMO "integer" can be removed, however I am
not sure how it effects data type system
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)