[ 
https://issues.apache.org/jira/browse/EMPIREDB-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rainer Döbele resolved EMPIREDB-192.
------------------------------------

       Resolution: Fixed
    Fix Version/s: empire-db-2.4.2

> Implement limitRows and skipRows for Oracle
> -------------------------------------------
>
>                 Key: EMPIREDB-192
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-192
>             Project: Empire-DB
>          Issue Type: Improvement
>    Affects Versions: empire-db-2.4.2
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.4.2
>
>
> Currently only limitRows is supported for Oracle with the limitation of a 
> potentially incorrect order of the rows.
> Properly implement limitRows and skipRows by wrapping the select command like 
> follows:
> for limit rows only:
> SELECT * FROM (
>   SELECT .... ORDER BY ...
> ) row_ WHERE rownum<={limit}
> for limitRows and skipRows:
> SELECT * FROM (SELECT row_.*, rownum rownum_ FROM (
>  SELECT .... ORDER BY ...
> )) row_ WHERE rownum<={skip+limit}) WHERE rownum_>{skip}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to