[
https://issues.jboss.org/browse/TEIID-1643?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1643:
---------------------------------------
You are expecting that:
a) the vendor/client wants the column label
b) the vendor/client expects getColumnName to report the column label - even though this
is not the case for other drivers
c) the vendor/client cannot change the call to getColumnLabel
It's not a question of whether that could happen, it's just a question of
prioritization. In general for other bugs we typically don't ask ourself if anyone is
dependent upon incorrect behavior. It seems needlessly proactive to offer a backwards
compatibility mode that no one may ever use given the workaround.
But just as I said above, if someone else provides a patch with docs, etc. then we can
certainly include it.
Teiid not qualifying returned result data element when AS used in
query
-----------------------------------------------------------------------
Key: TEIID-1643
URL:
https://issues.jboss.org/browse/TEIID-1643
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.5
Reporter: Warren Gibson
Assignee: Steven Hawkins
Attachments: QT_MySql50_Push.vdb
Not qualifying result data element when AS used in query. Example query below.
SELECT BQT1.SmallA.IntKey AS SmallA_IntKey, BQT2.MediumB.IntKey AS MediumB_IntKey FROM
BQT1.SmallA FULL OUTER JOIN BQT2.MediumB ON BQT1.SmallA.IntKey = BQT2.MediumB.IntKey WHERE
(BQT1.SmallA.IntKey >= 0) AND (BQT1.SmallA.IntKey <= 15) AND
(BQT2.MediumB.IntKey >= 5) AND (BQT2.MediumB.IntKey <= 20) ORDER BY
SmallA_IntKey, MediumB_IntKey
Actual Results:
<dataElement type="integer">IntKey</dataElement>
<dataElement type="integer">IntKey</dataElement>
Expected Results:
<dataElement type="integer">SmallA_IntKey</dataElement>
<dataElement type="integer">MediumB_IntKey</dataElement>
VDB attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira