[
https://issues.jboss.org/browse/TEIID-2281?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2281.
-----------------------------------
Resolution: Done
After testing with the 11.2 driver it seems that the initial fix was mostly sufficient.
Just getting the proper runtime type for nvarchar2 and varchar2 allowed them to bind
successfully as varchar. Contrary to the Oracle docs, attempting to bind nchar or
nvarchar using setObject with their respective java SQL type codes failed with invalid
column types.
Similar to TEIID-1952, It did look however that nchar needs to also be bound as a fixed
char to avoid padding issues. Also that previous fix needed expanded to cover Parameter
objects as well.
The designer issue is somewhat related in that the Designer import process will not
correctly type NVARCHAR2 nor VARCHAR2 columns. I'll send an issue their way.
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