[teiid-issues] [JBoss JIRA] (TEIID-5685) Allow for binding non-ascii strings as varchar

[Steven Hawkins (Jira)]

    [ https://issues.jboss.org/browse/TEIID-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707836#comment-13707836 ] 

Steven Hawkins commented on TEIID-5685:
---------------------------------------

The actual exception is:

ORA-01461: can bind a LONG value only for insert into a LONG column

This can occur when a varchar or nvarchar binding exceeds 4000 bytes.  For nvarchar that can happen for any string of 1333 characters or more depending on the particulars of the encoding (there are a lot of older oracle issues about this).

For char and nchar it can happen at 2000 bytes, with a similar limitation around the character conversion for nchar.


> 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.



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