[
https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-2460:
------------------------------------------
If BigInteger is the datatype, then I'm not sure we can assume
it's an "int"?
Generally information about the design time type is not exposed by DatabaseMetaData - only
the runtime type. Our BigInteger columns would have a type code of Numeric in the
DatabaseMetaData. You have to go off of the type name, the java classname, or the scale
to infer that it's a biginteger column. There is nothing to indicate that the design
time type is integer.
So if the source vdb had design time type integer, which is the runtime type biginteger,
then I don't see a problem with reimporting it as 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, TEIIDDES2460.zip
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)