[teiid-designer-issues] [JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
[
https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu...
]
Andrej Šmigala edited comment on TEIIDDES-2460 at 8/4/15 2:59 AM:
------------------------------------------------------------------
Designer still sets the datatype to biginteger when the datatype in the deployed vdb is
integer.
bq. 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.
bq. On re-import (deployed) VDB, the imported type is "integer" which is
Teiid's runtime type which is supported for legacy purposes
I can create a table, set the datatype to int, create and deploy vdb, import through jdbc
(the imported model has the the datatype set to integer), create and deploy another vdb
with the new model and import through jdbc again. The second imported model has the
datatype set to biginteger.
I agree this is a rather convoluted use-case, but it is not unthinkable that the user has
an older vdb (created in previous versions of designer) deployed and is trying to import
it.
was (Author: asmigala):
Designer still sets the datatype to biginteger when the datatype in the deployed vdb is
integer.
bq. 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.
bq. On re-import (deployed) VDB, the imported type is "integer" which is
Teiid's runtime type which is supported for legacy purposes
I can create a table set the datatype to int, create and deploy vdb, import through jdbc
(the imported model has the the datatype set to integer), create and deploy another vdb
with the new model and import through jdbc again. The second imported model has the
datatype set to biginteger.
I agree this is a rather convoluted use-case, but it is not unthinkable that the user has
an older vdb (created in previous versions of designer) deployed and is trying to import
it.
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.0.3, 9.2
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)