You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Xiaoqin Feng (JIRA)" <ji...@apache.org> on 2008/02/21 21:31:19 UTC

[jira] Updated: (OPENJPA-521) Collection ordering doesn''t work if the cache is enabled

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

Xiaoqin Feng updated OPENJPA-521:
---------------------------------

    Remaining Estimate: 168h  (was: 0.12h)
     Original Estimate: 168h  (was: 0.12h)

> Collection ordering doesn''t work if the cache is enabled
> ---------------------------------------------------------
>
>                 Key: OPENJPA-521
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-521
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache
>    Affects Versions: 0.9.7, 1.0.0, 1.0.1, 1.0.2
>         Environment: Kodo4.1.4 with OpenJPA1.0.0
>            Reporter: Xiaoqin Feng
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> In a use case that has 2 persistence classes - parent and child.  Parent and child is one-many relationship. 
> Parent entity has a collection of children.
> When order-by is set for collection of children and data cache is enabled, inserting children, updating children's field value that is used by ordering will cause collection out of order. But data cache doesn't aware this and returned out of order collection.
> If data cache is disabled, it always use SQL query with "ORDER BY" applied so collection is returned in correct order.
> Test case will be attached.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.