[
https://issues.apache.org/jira/browse/OPENJPA-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-845:
---------------------------------
Fix Version/s: 2.0.0-M1
> 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
> Fix For: 2.0.0-M1
>
>
> 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.
