Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Fri, 12 Oct 2012 10:33:03 +0000 (UTC)
From: =?utf-8?Q?C=C3=A9dric_Damioli_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <982909682.36773.1350037983345.JavaMail.jiratomcat@arcas>
In-Reply-To: <695708416.21096.1349892063794.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (JCR-3443) Normalize String properties when
 ordering query results
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/JCR-3443?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:all-tabpanel ]

C=C3=A9dric Damioli updated JCR-3443:
--------------------------------

    Attachment:     (was: normalize.patch)
   =20
> 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=C3=A9dric Damioli
>
> 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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira