[
https://issues.jboss.org/browse/TEIID-5687?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5687.
-----------------------------------
Resolution: Done
Resolving as a known issue. Oracle does not provide a good facility for this. If we bind
as a fixed character string, then there is a character conversion. If we bind as nchar,
the padding can be off. We can try to get the padding from the length, but that gets
complicated for longer values. The database has a limit of 2000 chars and 2000 bytes, so
it depends upon the encoding to determine what the actual padding could be.
Oracle comparison with binding of nchar with non-ascii chars is not
correct
---------------------------------------------------------------------------
Key: TEIID-5687
URL:
https://issues.jboss.org/browse/TEIID-5687
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
An nchar column binding in the where clause will use the FIXED_CHAR (999) oracle type -
however that converts the value to ascii, which may result in invalid results:
nchar_col = ?
where ? is bound to Ā would search instead for A.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)