You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2008/06/10 23:33:44 UTC
[jira] Closed: (OPENJPA-632) setFirstResult and setMaxResults not
working for Oracle.
[ https://issues.apache.org/jira/browse/OPENJPA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Dick closed OPENJPA-632.
--------------------------------
Resolution: Fixed
Assignee: Michael Dick
Reposting the comments Marc made when he committed rev 584463 for posterity :
"The overridden toSelect() signature in the OracleDictionary was no longer appropriate since the DBDictionary.toSelect() change in revision #577972 (which fixed OPENJPA-378). This resulted in the special Oracle range handing to no longer take place, resulting in setFirstResult() and setMaxResults() effectively being ignored for Oracle."
> setFirstResult and setMaxResults not working for Oracle.
> --------------------------------------------------------
>
> Key: OPENJPA-632
> URL: https://issues.apache.org/jira/browse/OPENJPA-632
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 1.0.1, 1.0.2
> Reporter: Michael Dick
> Assignee: Michael Dick
> Fix For: 1.0.3
>
>
> Marc caught this problem a few months ago and fixed it in trunk. I've discovered that the problem exists in 1.0.x as well and I'm porting the fix.
> I believe we already have sufficient test coverage - but we need to run the regression bucket more regularly on licensed databases (ie Oracle, DB2).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.