[
https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2398:
----------------------------------------
The problem we're getting into is that Designer is still supporting more and different
datatypes than the Teiid Runtime.
For example the SMALLINT and INT types below end up with different Design-time types:
JDBC Import >>>
| *NATIVE TYPE* | *JDBC Type* | *Design Time Type* |
| SMALLINT | SMALLINT | *short* |
| INT | INT | *int* |
Teiid Connection Import >>>
| *NATIVE TYPE* | *DDL Type* | *Design Time Type* |
| SMALLINT | integer | *int* |
| INT | long | *long* |
So we can change the JDBC mapping to try and match the Teiid Runtime type, but all it has
is NATIVE TYPE, but maybe that's enough?
Inconsistent column datatypes when importing
--------------------------------------------
Key: TEIIDDES-2398
URL:
https://issues.jboss.org/browse/TEIIDDES-2398
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export, Modeling
Reporter: Andrej Šmigala
Assignee: Mark Drilling
Fix For: 9.1, 9.0.2, 8.6.2
Attachments: datatypes.png, MySQL_BQT_DDL.ddl
There are multiple discrepancies in the column datatypes when importing using JDBC
importer vs when using Teiid Connection importer.
Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all
numeric datatypes in oracle)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)