[
https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu...
]
Barry LaFond edited comment on TEIIDDES-2256 at 7/21/14 10:22 AM:
------------------------------------------------------------------
Our design-time types are defined here:
https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org....
Except for adding *varbinary* 2 years ago, nothing's been changed for quite some time.
1) Would it be safe to just remove the xs:biginteger?
2) Maybe just adding a validation warning (deprecate?) would be enough?
3) Could you check this schema for any other types that should be there?
was (Author: blafond):
Our design-time types are defined here:
https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org....
Except for adding *varbinary* 2 years ago, nothing's been changed for quite some time.
1) Would it be safe to just remove the xs:biginteger?
2) Could you check this schema for any other types that should be there?
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)
Reporter: Ramesh Reddy
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.2.6#6264)