[
https://issues.jboss.org/browse/TEIIDDES-2061?page=com.atlassian.jira.plu...
]
Van Halbert commented on TEIIDDES-2061:
---------------------------------------
I disagree, char(length) in the database should be supported. Designer works right in
importing as char and capturing its length and that its fixed. That is the basis for
char versus varchar, is that char is for fixed length values. The server / translator
should be changed so support the length of a char, and not chop off at 1 char.
We can't go making existing databases change the char(length) columns to fix us. Its
an existing feature.
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+] to see if a conversion to varchar[n+] is
needed.
--
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