[
https://issues.jboss.org/browse/TEIIDDES-2061?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-2061:
------------------------------------------
So is the issue with the importer, that it should be converting
char[n] to String types, rather than char?
If it's importing as char, then yes that's an issue.
Is this why the data is being truncated?
The engine will always attempt to convert the incoming data to the runtime datatypes. So
yes we'll take the String value and convert it into a Character.
If it is, just curious on how teiid handles querying the char[n]
column that is an index?
The issue is well beyond just using an index. Depending upon the situation we'll
either attempt to widen the column, or we'll use the narrowed comparison value. So
issues abound when the type mapping is off.
char[n+] field is truncated by importer
---------------------------------------
Key: TEIIDDES-2061
URL:
https://issues.jboss.org/browse/TEIIDDES-2061
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Affects Versions: 8.3.1
Reporter: Johnathon Lee
Attachments: testErrors.vdb
truncation of Char[>1] fields to one character.
reproduction with simple VDB (to be attached):
SELECT asChar,asVarChar,asInt FROM "TestErrors"."TruncateCHAR";
the "asChar" field only returns a "C" and the asVarChar returns
the complete value.
That is the expected behavior, per the Data Virtualization Reference Manual, char
datatype is a single Unicode character (java.lang.Character). However, the importer may
need to check for the occurrence of char[n+] and not assume char[1].
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira