Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of marcel.reutegger@gmx.net
 designates 213.165.64.20 as permitted sender)
Message-ID: <47E8F06C.4040901@gmx.net>
Date: Tue, 25 Mar 2008 13:30:36 +0100
From: Marcel Reutegger <marcel.reutegger@gmx.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: users@jackrabbit.apache.org
Subject: Re: problem with SQL query that uses  "contains" function
References: 
 <OFCCC2DE36.32C59B64-ON85257416.0075CAA2-85257416.00768662@pointalliance.com>
In-Reply-To: 
 <OFCCC2DE36.32C59B64-ON85257416.0075CAA2-85257416.00768662@pointalliance.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Lei Zhou wrote:
> select * from my:nodeType where jcr:path LIKE '/my:root/contents/%' AND 
> my:state='published' AND contains(., 'account')
> 
> When I run it against the repository, from time to time, the resultset may 
> contain some entries that doesn't match the condition "contains(., 
> 'account')" at all.
> 
> Is this a bug or something I just didn't pickup? 

I'm not aware of a bug that would cause this kind of behaviour.

however, it may happen that while you iterate through the result set another 
session modifies one of the result nodes. thus, it may appear that a node does 
not match the query, even though it did at the time when Query.execute() was called.

regards
  marcel