[
https://issues.apache.org/jira/browse/JCR-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084218#comment-13084218
]
Jukka Zitting commented on JCR-3047:
------------------------------------
To properly implement the mapping from an Ordering to a Lucene SortField you'd
need to consider also other information than just the property name. For
example "ORDER BY UPPER(pname)" or "ORDER BY LENGTH(pname)" must be handled
differently from "ORDER BY pname", and an ordering like "ORDER BY b.pname"
can't be used if you're constructing the Lucene query for selector a. Thus I
don't think an isolated method like getAffectedPropertyName() really serves a
useful purpose.
> OperandEvaluator should be able to handle Nodes as well, not just Rows
> ----------------------------------------------------------------------
>
> Key: JCR-3047
> URL: https://issues.apache.org/jira/browse/JCR-3047
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-jcr-commons
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Trivial
> Fix For: 2.3.0
>
> Attachments:
> 0001-JCR-3047-OperandEvaluator-should-be-able-to-handle-N.patch
>
>
> OperandEvaluator is used to evaluate Operands values against given Rows, and
> in an effort to improve the sorting part of SQL2 (JCR-2959), I need it to
> handle plain Nodes as well.
> This is a small change, as the OperandEvaluator already extracts the Node
> info from the Row, so there is no obvious reason no to expose the Node
> operations directly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
