[
https://jira.jboss.org/jira/browse/TEIID-728?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIID-728:
--------------------------------------
This is not a regression and is actually a problematic issue. We are currently trimming
strings based upon the resultset metadata type being CHAR. More than just Oracle reports
the return type of a selected string literal as CHAR (DB2/Derby). We can do a better job
about not pushing select literals, but some situations (for example pushed unions) are
unavoidable. The best approach at the connector level is probably to check for a native
type of CHAR and to wrap the column in an rtrim. Regardless pushing a string literal with
end spaces with trim strings as a connector binding setting turned on will truncate them.
Pushing blank-padded literals to source may fail to return correct
results
--------------------------------------------------------------------------
Key: TEIID-728
URL:
https://jira.jboss.org/jira/browse/TEIID-728
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.2.0
Environment: fedora 10, JDK 1.6, Teiid from 7/16/2009
Reporter: Paul Nittel
Assignee: Steven Hawkins
Fix For: 6.2.0
While reviewing possible CTC errors, it was noticed that SPACE(n) was not returning the
number of spaces specified. We did see that going directly to Oracle worked correctly.
Steve H. believes Oracle is returning a CHAR type and Teiid is trimming the values as a
result. (It would not have if the return type was VARCHAR, like SQL Server returns.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira