openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-165) QueryImpl.setFirstResult does not take already set maxResults into account
Date Tue, 07 Aug 2007 17:19:59 GMT

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

Patrick Linskey updated OPENJPA-165:
------------------------------------

    Fix Version/s:     (was: 0.9.8)
                   1.0.0

> QueryImpl.setFirstResult does not take already set maxResults into account
> --------------------------------------------------------------------------
>
>                 Key: OPENJPA-165
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-165
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: query
>    Affects Versions: 0.9.7
>            Reporter: Jonathan Feinberg
>            Assignee: Kevin Sutter
>             Fix For: 1.0.0
>
>
> If you want rows 10-19 of some query, the sequence
>   q.setFirstResult(10).setMaxResults(10);
> behaves as expected. On the other hand
>   q.setMaxResults(10).setFirstResult(10);
> returns the empty list. QueryImpl.setFirstResult should reset the range endpoint. maxResults
is a count, not an index.

-- 
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