[
https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2018:
----------------------------------------
In the image:
* ALL_TYPES_JDBC is imported via JDBC importer
* ALL_TYPES_TEIID is imported via Teiid Connection Importer which operates on the above
DDL during that import.
We do not currently map the DDL column datatypes in the Teiid Connection importer. Hence,
"integer" results in the built-in-type "integer".
So what should the mappings be? And is our JDBC importer mapping types correctl?
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