You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2010/04/21 11:36:49 UTC
[jira] Updated: (EMPIREDB-62) Allow to set limit for maximum number
of rows returned
[ https://issues.apache.org/jira/browse/EMPIREDB-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francis De Brabandere updated EMPIREDB-62:
------------------------------------------
Fix Version/s: empire-db-2.0.7-incubating
(was: empire-db-2.0.6-incubating)
moving to 2.0.7
> 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.