[
https://issues.jboss.org/browse/TEIIDDES-2061?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-2061:
------------------------------------------
Sorry to be pedantic, but everyone needs to make sure to not just say char, int, etc., but
to be specific as to the domain in which the data type term is applicable.
If we're converting from char[n] to String, I thought that was
the solution to NOT truncate.
Just to clarify, we're saying that the importer will import a database char[n] where n
is != 1 to a Teiid String, which is not typically truncated (but may be in some situations
with long string values).
So why a rule to say it will be truncated.
His intent is likely to highlight a modeling error with using a Teiid char possibly
introduced by this bug or unintentionally by the user.
Can there also be a rule put in place in designer such that if char
data type is used, that length cannot be changed from 1?
That would also help.
char[n+] field is truncated by importer
---------------------------------------
Key: TEIIDDES-2061
URL:
https://issues.jboss.org/browse/TEIIDDES-2061
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.3.1
Reporter: Johnathon Lee
Assignee: Barry LaFond
Fix For: 8.4, 8.3.2
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