[
https://jira.jboss.org/jira/browse/TEIID-947?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-947.
----------------------------------
Fix Version/s: 7.0
Resolution: Done
If the metadata call is made after the command is planned, then a bug with the SetQuery
clone could allow it to report the wrong types. That has now been fixed.
UNION query with different datatypes on each side of UNION is
producing inconsistent results
---------------------------------------------------------------------------------------------
Key: TEIID-947
URL:
https://jira.jboss.org/jira/browse/TEIID-947
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Warren Gibson
Assignee: Steven Hawkins
Fix For: 7.0
The following query is producing unexpected results in CTC. It is not consistent and
sometimes produces unexpected results and sometimes passes. However, it can be
reproduced.
SELECT IntKey, IntNum FROM BQT1.SmallA UNION SELECT StringKey, StringNum FROM
BQT2.MediumB ORDER BY IntKey
The datatypes of each side of the union are not the same and sometimes
rmdata.getColumnTypeName(++col) indicates its a string and sometimes it says its an
integer.
It is my understanding that the column should be implicitly converted to a consistent
type (in this case a string).
--
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