Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <234594718.1203684499303.JavaMail.jira@brutus>
Date: Fri, 22 Feb 2008 04:48:19 -0800 (PST)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1408) Invalid query results when using
 jcr:like with a case transform function and a pattern not starting with a
 wildcard
In-Reply-To: <1192189714.1203623719345.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Marcel Reutegger updated JCR-1408:
----------------------------------

    Fix Version/s: core 1.4.2

Merged change into 1.4 branch in revision: 630183

> Invalid query results when using jcr:like with a case transform function =
and a pattern not starting with a wildcard
> -------------------------------------------------------------------------=
------------------------------------------
>
>                 Key: JCR-1408
>                 URL: https://issues.apache.org/jira/browse/JCR-1408
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, query
>    Affects Versions: 1.4, core 1.4.1
>         Environment: Ubuntu gutsy, Sun JDK 1.5.0_08
>            Reporter: S=C3=A9bastien Launay
>             Fix For: core 1.4.2, 1.5
>
>         Attachments: jackrabbit-1.4.x-query-like.patch
>
>
> If the repository contains nodes with the following value for the propert=
y name :
> john
> JOhn
> joe
> Joey
> and we run the following query :
> //element(*, document)/*[jcr:like(fn:lower-case(@name), 'joh%')]")
> then all the previous nodes will match especially the last 2 nodes.
> The reason is the use of two range scans from the lucene term index:
> ..._name_jOH
> ..................
> ..._name_joh_
> and
> ..._name_JOH
> ..................
> ..._name_Joh_
> The first range will contains ..._name_joe property and the second will c=
ontains ..._name_Joey.
> But the pattern 'joh%' and so the regexp '.*' because of the range scan w=
ill match
> the substring values of the properties ('' in the first range and 'y' in =
the second range).
> The solution is to use the full pattern (ie 'joh.*') for matching each pr=
operties.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.