[
https://issues.apache.org/jira/browse/CAY-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrus Adamchik closed CAY-1539.
--------------------------------
Resolution: Fixed
Fix Version/s: 3.1M3
I was able to reproduce this problem in a test case (r1150328). The patch fixes
it, so I committed it. Thanks as usual!
(may think of backporting that to 3.0??)
> Incorrect offset handling on some queries against database with supported
> LIMIT/OFFSET clauses
> ----------------------------------------------------------------------------------------------
>
> Key: CAY-1539
> URL: https://issues.apache.org/jira/browse/CAY-1539
> Project: Cayenne
> Issue Type: Bug
> Components: Database integration
> Affects Versions: 3.1M1
> Environment: Apache Cayenne 3.1-SNAPSHOT from trunk, PostgreSQL 8.4.
> Reporter: Victor Antonovich
> Fix For: 3.1M3
>
> Attachments: select_action_offset_handling.patch
>
>
> Select queries with offset set and suppressed DISTINCT clause running against
> database like PostgreSQL (with OFFSET/LIMIT clauses supported) are handled
> incorrectly. Now, DISTINCT suppressing in SelectTranslator also suppress
> LIMIT/OFFSET SQL query clauses, but in-memory offset returned by
> SelectAction.getInMemoryOffset() remain unchanged, effectively zeroing offset
> for these queries against databases like PostgreSQL.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
