[
https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2018:
----------------------------------------
The intent is to be consistent. In this case I have a SQL Server DB with a BQT table. If I
import a column type *int* via JDBC importer, I end up with a design-time type of *int*.
If I import via TEiid connection/DDL, the column datatype is defined as *integer*.
Currently we set the design-time type to *integer*. So the 2 relational columns end up
with different datatypes.
I'm assuming for the moment that our JDBC importer is setting the property design-time
type.
The runtime type is determined at index time via a SqlAspect.getRuntimeTypeName(EObject
type) which eventually walks the datatype hiearchy to get the base type. (I'll verify
that tomorrow)
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