[
https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu...
]
Barry LaFond resolved TEIIDDES-2460.
------------------------------------
Resolution: Out of Date
Retesting resulted in the imported datatype is "integer".
Note that Designer was changed in 9.x to not allow selecting the "integer"
datatype. So the use-case was changed to define both *int* and *string* typed columns.
On re-import (deployed) VDB, the imported type is "integer" which is Teiid's
runtime type which is supported for legacy purposes. There is no way to tell what the
original datatype from the original VDB because Teiid converts it via their JDBC
metadata.
marking as Out Of Date
JDBC Importer changes integer type to biginteger type when importing
schema (reusing) from VDB
-----------------------------------------------------------------------------------------------
Key: TEIIDDES-2460
URL:
https://issues.jboss.org/browse/TEIIDDES-2460
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 9.2, 9.0.3
Attachments: ErrorDialog.png
When the JDBC importer is used to import a schema from an existing VDB integer types will
be converted into biginterger types. This error is similar to Bug 1026892 except no
exception is raised
Version-Release number of selected component (if applicable):
Actual results:
Imported schema has changed integer data type to biginteger data type.
Expected results:
Imported schema will be identical to original schema.
Additional info:
Imported schema is so long as the JPA entity reflects the biginteger type. This is
problematic because now two separate JPA entities are needed, one for the original schema
and another for the imported schema.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)