[
https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu...
]
Andrej Šmigala reopened TEIIDDES-2460:
--------------------------------------
Importing with JDBC importer still changes integer to biginteger.
It is no longer possible to create new models with the integer datatype (designer uses int
instead).
However, this might still be a problem if a user wants to import (reuse) from an older vdb
created in previous versions of designer (one such vdb is attached).
Steps to reproduce in current designer:
# import the attached model
# notice the table t1 in the source model has column c1 : integer
# execute the vdb
# Import from JDBC, select the vdb connection profile, check "Import as VDB source
model"
# finish the import, notice the t1 table in the new model has column c1 : biginteger
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)