[
https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2256:
----------------------------------------
{code:xml}
<xs:simpleType mmedt:UUID="mmuuid:822b9a40-a066-1e26-9b08-d6079ebe1f0d"
mmedt:runtimeDataType="biginteger" mmedt:runtimeDataTypeFixed="false"
name="biginteger">
<xs:annotation>
<xs:appinfo/>
<xs:documentation>[Definition:] biginteger represent
arbitrary-precision integers. All operations behave as
if bigintegers were represented in two's-complement
notation (like Java's primitive integer
types).</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:decimal"/>
</xs:simpleType>
{code}
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)