-
Bug
-
Resolution: Done
-
Major
-
None
-
None
Older oracle drivers, such as 11.2.0.1.0 do not accept the sql type NVARCHAR as an argument to set object, which results in an exception like:
Caused by: java.sql.SQLException: Invalid column type at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:12187) at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:11577) at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:12286) at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:548) at org.teiid.translator.jdbc.JDBCExecutionFactory.bindValue(JDBCExecutionFactory.java:1145)
We can also safely narrow our usage of the n types with oracle as anything in the latin 1 supplement is still allowed in varchar values.
- is related to
-
TEIID-5313 Oracle translator issue with mixing string types and general issues with non-ascii strings
- Resolved