empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] Closed: (EMPIREDB-62) Allow to set limit for maximum number of rows returned
Date Sun, 07 Nov 2010 14:09:07 GMT

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

Rainer Döbele closed EMPIREDB-62.
---------------------------------

    Resolution: Fixed

function limitRows() on DBCommand has been implmented for the following databases:
- MySQL
- Microsoft SQL Server
- Oracle

Additionally the function skipRows() is available for MySQL.

Availability may be checked like this:

if (db.getDriver().isSupported(DBDriverFeature.QUERY_LIMIT_ROWS))
or
if (db.getDriver().isSupported(DBDriverFeature.QUERY_SKIP_ROWS))


> Allow to set limit for maximum number of rows returned
> ------------------------------------------------------
>
>                 Key: EMPIREDB-62
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-62
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: empire-db-2.0.6-incubating
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>             Fix For: empire-db-2.0.7-incubating 
>
>
> Currently it is not possible to limit the number of rows returned by a query.
> The question is whether to add it to ths sql phrase or use setMaxRows() before executing
the statement.
> SQL is somewhat different for each database vendor:
> SQL Server:
> SELECT TOP 10 id, name, ...
> FROM contacts
> MySQL:
> SELECT id, name, ...
> FROM contacts
> LIMIT 10
> ORACLE:
> SELECT id, name, ...
> FROM contacts
> WHERE ROWNUM <= 10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message