[
https://issues.apache.org/jira/browse/JCR-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474166#comment-13474166
]
Cédric Damioli commented on JCR-3443:
-------------------------------------
well, that's why I called the function normalize ;)
Collating is about comparing strings, so I think that does not fit well with a
function, applied to only one string at a time.
In XPath 2.0 one can specify a collation URI in the "order by" clause. We could
implement this in jackrabbit as well, but that does not translate well in SQL,
or QOM, ...
I agree with you that a true collation would be great, but maybe could the
normalization be seen as a first step, much easier to implement and to use ?
> Normalize String properties when ordering query results
> -------------------------------------------------------
>
> Key: JCR-3443
> URL: https://issues.apache.org/jira/browse/JCR-3443
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, query
> Reporter: Cédric Damioli
> Attachments: normalize.patch
>
>
> Properties containing non-ASCII characters are not well collated in query
> results
> There's only two allowed functions so far in XPath (fn:lower-case and
> fn:upper-case). There exists the equivalent LOWER and UPPER in SQL
> I propose to add a fn:normalize (resp NORMALIZE) function giving expected
> results
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
