[
https://issues.jboss.org/browse/TEIID-1545?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1545:
---------------------------------------
uncorrelated scalar subquery planning allows the expression to be seen as basically a
simple scalar. When correlated the planner leaves the projection in place above the
access to DB2 and does not consider pushing the order by.
The fix for TEIID-1529 could be expanded quite easily to handle this case as well.
Order By not pushed down
------------------------
Key: TEIID-1545
URL:
https://issues.jboss.org/browse/TEIID-1545
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Mark Addleman
Assignee: Steven Hawkins
ORDER BY is not pushed down in the following query:
SELECT J0.APPNAME, B.\"SYSID\", B.\"USERID\",
(select count(*) from (select * from notes.RETRIEVE_NOTES where OBJECT_PKEY = B.USERID)
as foo) as C_notesForObject
FROM \"SECURITY.BASEUSER\" as B left join security.sysinfo J0 on
J0.sysid=B.sysid ORDER BY J0.APPNAME ASC
SECURITY comes from the DB2 translator
notes comes from a programmatic translator which does not support ORDER BY
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira