You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Jonathan Feinberg (JIRA)" <ji...@apache.org> on 2007/03/09 19:07:09 UTC
[jira] Created: (OPENJPA-165) QueryImpl.setFirstResult does not
take already set maxResults into account
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
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.
[jira] Assigned: (OPENJPA-165) QueryImpl.setFirstResult does not
take already set maxResults into account
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter reassigned OPENJPA-165:
------------------------------------
Assignee: Kevin Sutter
> 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
> Assigned To: Kevin Sutter
>
> 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.
[jira] Updated: (OPENJPA-165) QueryImpl.setFirstResult does not
take already set maxResults into account
Posted by "Kevin Sutter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Sutter updated OPENJPA-165:
---------------------------------
Fix Version/s: 0.9.7
I've discussed this problem with Jonathan and we should have a patch available soon.
> 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
> Assigned To: Kevin Sutter
> Fix For: 0.9.7
>
>
> 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.