[
https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-2018:
------------------------------------------
Q: Should the Teiid Import option look at native type (i.e. int) and
use that instead? or map integer >> int
I'm not sure what you mean. We need to be consistent here with there the type names
come from. From a teiid/sql perspective int/integer are just synonyms. So I'm not
sure by what you mean by map integer to int, double to float, etc. You have to say what
domain each of the terms apply to. From there we can say things like teiid double = sql
server float, xsd integer = teiid biginteger, and so on and so forth.
Generally the DDL importer when importing Teiid DDL should always use the Teiid type as
the runtime type. The native type is not necessary in making the determination.
DDL importer creates wrong data type for "integer"
--------------------------------------------------
Key: TEIIDDES-2018
URL:
https://issues.jboss.org/browse/TEIIDDES-2018
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3
Reporter: Ramesh Reddy
Assignee: Barry LaFond
Fix For: 8.4
Attachments: types_comparison.png
When using the Teiid Designer's "DDL importer" or "Teiid Connection
>> Source Model",
* if the DDL supplied is "Teiid" dialect
* if the data type supplied is "integer"
Then the resulting data type of the column/parameter is mapped "xs:decimal"
which is aliased as "integer", which results in "big integer" at run
time.
This should be mapped to "xs:long" which is aliased as "int". The
confusing thing is there is also "xs:integer" which is aliased to
"long"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira