[teiid-issues] [JBoss JIRA] (TEIID-5587) Oracle 11 drivers don't accept NVARCHAR type

[Steven Hawkins (Jira)]

     [ https://issues.jboss.org/browse/TEIID-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-5587.
-----------------------------------
    Resolution: Done


Changed the logic to only use the NVARCHAR type when a character is beyond the 255 code point.

> Oracle 11 drivers don't accept NVARCHAR type
> --------------------------------------------
>
>                 Key: TEIID-5587
>                 URL: https://issues.jboss.org/browse/TEIID-5587
>             Project: Teiid
>          Issue Type: Bug
>          Components: JDBC Connector
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>            Priority: Major
>             Fix For: 12.0, 11.2.2
>
>
> 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:
> {code}
> 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)
> {code}
> 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.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)