You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cayenne.apache.org by "Victor Antonovich (JIRA)" <ji...@apache.org> on 2011/02/10 10:26:57 UTC

[jira] Updated: (CAY-1539) Incorrect offset handling on some queries against database with supported LIMIT/OFFSET clauses

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

Victor Antonovich updated CAY-1539:
-----------------------------------

    Attachment: select_action_offset_handling.patch

Proposed patch attached.

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