Mailing-List: contact commits-help@empire-db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@empire-db.apache.org
Date: Fri, 13 Sep 2013 10:34:51 +0000 (UTC)
From: =?utf-8?Q?Rainer_D=C3=B6bele_=28JIRA=29?=
 <empire-db-dev@incubator.apache.org>
To: empire-db-commits@incubator.apache.org
Message-ID: <JIRA.12668453.1379068420502.128467.1379068491560@arcas>
In-Reply-To: <JIRA.12668453.1379068420502@arcas>
References: <JIRA.12668453.1379068420502@arcas>
Subject: [jira] [Created] (EMPIREDB-192) Implement limitRows and skipRows
 for Oracle
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Rainer D=C3=B6bele created EMPIREDB-192:
--------------------------------------

             Summary: 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=C3=B6bele
            Assignee: Rainer D=C3=B6bele


Currently only limitRows is supported for Oracle with the limitation of a p=
otentially incorrect order of the rows.
Properly implement limitRows and skipRows by wrapping the select command li=
ke follows:
for limit rows only:
SELECT * FROM (
  SELECT .... ORDER BY ...
) row_ WHERE rownum<=3D{limit}

for limitRows and skipRows:
SELECT * FROM (SELECT row_.*, rownum rownum_ FROM (
 SELECT .... ORDER BY ...
)) row_ WHERE rownum<=3D{skip+limit}) WHERE rownum_>{skip}


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira