[teiid-issues] [JBoss JIRA] (TEIID-4888) Support for SetQueryLimit
[
https://issues.jboss.org/browse/TEIID-4888?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4888.
-----------------------------------
Resolution: Done
Added a new capability supportsSetQueryLimitOffset to handle this issue. This may still
not exactly match openedge as it appears that cursor operations must be restricted to a
top level select with other restrictions. This change will only prevent the placement
directly on a set query, but if views are supported or the limit is pushed further it
could still be placed in nested selects.
Support for SetQueryLimit
-------------------------
Key: TEIID-4888
URL: https://issues.jboss.org/browse/TEIID-4888
Project: Teiid
Issue Type: Feature Request
Components: JDBC Connector
Reporter: German Tejero
Assignee: Steven Hawkins
Priority: Minor
Fix For: 10.0
OpenEdge RDBMS not support fetch/offset in a set query. For example, the generated SQL:
SELECT
g_1.ejer AS c_0
FROM PUB.modpre AS g_1
UNION ALL
SELECT
g_0.ejer AS c_0
FROM PUB.modesp AS g_0
FETCH NEXT 100 ROWS ONLY
For the view:
CREATE VIEW Modificaciones(
ejercicio INTEGER
)AS SELECT T.ejercicio
FROM(
SELECT M.ejercicio,
FROM sipbas.modesp AS M
UNION ALL
SELECT M.ejercicio
FROM sipbas.modpre AS M) AS T;
It is necessary to be able to indicate SetQueryLimit in the same way as with
SetQueryOrderBy.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)