[
https://issues.apache.org/jira/browse/JCR-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769133#action_12769133
]
Marcel Reutegger commented on JCR-952:
--------------------------------------
> What I don't understand is, why is this issue open for 2,5 years already?
because nobody provided a patch
> And why is it a minor issue?
because this is a feature that is not part of the JCR specification.
> As far as I'm concerned, this is a major issue.
Feel free to contribute a patch.
> Can this be easily solved?
It is actually solved already. At least partially. Using JQOM or JCR_SQL2 you
already have the ability to use a lower/upper case function in the order by
clause. XPath and SQL (the query syntax defined in JCR 1.0) do not support them
yet.
See classes LowerCaseSortComparator and UpperCaseSortComparator in
jackrabbit-core. The parsers for XPath and SQL are in the module spi-commons.
> Support lower and upper case functions in "order by" clause
> -----------------------------------------------------------
>
> Key: JCR-952
> URL: https://issues.apache.org/jira/browse/JCR-952
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-core, query
> Affects Versions: 1.3
> Reporter: James Hang
> Priority: Minor
>
> The query languages should support lower- and upper-case functions within the
> "order by" clause. This would provide case-insensitive ordering of query
> results.
> Example: Find all "nt:base" nodes ordered by the "foo" property, but
> ignoring case
> In XPath:
> //element(*,nt:base) order by fn:lower-case(@foo)
> In SQL:
> SELECT * FROM nt:base ORDER BY lower(foo)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
