You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2009/02/26 18:15:10 UTC

[jira] Resolved: (OPENJPA-845) Ordering across slice fails when ordering terms are not included in projection items

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

Pinaki Poddar resolved OPENJPA-845.
-----------------------------------

    Resolution: Fixed

> Ordering across slice fails when ordering terms are not included in projection items
> ------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-845
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-845
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: slice
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>
> Query 1: select p from Person p ORDER BY p.name
> Query 2: select p, p.name from Person p ORDER BY p.name
> Query 1 fails, Query 2 succeeds. The in-memory ordering required for Query 1 in terms needed to extract the ordering value p.name from a Person p. That logic is broken for PCPath (i.e. p.name). Inheritance hierarchy of PCPath was changed (with certain reservation as it went against the norm) to extend kernel.exps.CandidatePath so that in-memory value evaluation logic can be reused. However, the logic for CandidatePath does not work for PCPath because the internal representation of the path vary (Traversal vs. Action) and are unrelated. The result is a class cast exception (thanks to Fernando who tracked the error down).       

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