[teiid-issues] [JBoss JIRA] (TEIID-2281) Exception when updating Oracle NVARCHAR2 columns (Teiid embedded)
[
https://issues.jboss.org/browse/TEIID-2281?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2281:
----------------------------------
Fix Version/s: 8.2
There are two issues here. The first is that nvarchar2 and varchar2 should be imported as
strings, but there's no logic checking for the mapping of those oracle specific
types.
The other issue is similar to some of the workaround logic that was added for oracle fixed
type handling where for the purposes of binding we need to know the real parameter type.
The current logic really needs a bit of an overhaul to support this generally as only the
object value and Teiid class are passed into the bind method. We'll need to
generalize this a little. This second part may not make it into 8.2.
Exception when updating Oracle NVARCHAR2 columns (Teiid embedded)
-----------------------------------------------------------------
Key: TEIID-2281
URL: https://issues.jboss.org/browse/TEIID-2281
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 8.1
Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0
Reporter: I Leitch
Assignee: Steven Hawkins
Fix For: 8.2
The TEIID jdbc driver returns SQLType of “JAVA_OBJECT” for NVARCHAR, so it throws and
exception in Oracle JDBC call “setObject(i,param,TYPE.JAVA_OBJECT)”.
We can reproduce the same exception using the Oracle jdbc driver by making the same
setObject call.
This is happening using Teiid embedded but also happens with a dynamic vdb in XML. We
have not tried a designer-created vdb.
Discussion:
https://community.jboss.org/message/772860#772860
Possibly related:
https://issues.jboss.org/browse/TEIIDDES-179
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira