]
Steven Hawkins resolved TEIID-5685.
-----------------------------------
Resolution: Done
Changed the logic to associate a varchar type with oracle insert literals and parameters
to prevent using nvarchar bindings.
Allow for binding non-ascii strings as varchar
----------------------------------------------
Key: TEIID-5685
URL:
https://issues.jboss.org/browse/TEIID-5685
Project: Teiid
Issue Type: Quality Risk
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
Related to TEIID-5587, even newer oracle drivers that do support NVARCHAR will throw an
exception when the number of bytes in an NVARCHAR string exceeds 4000.
In situations, such as insert, where the underlying native type can be detected, we can
simply bind as VARCHAR if it's not a multi-byte type - and log that the string will
have replacement characters.