Re: XQuery 'Select Parent' Syntax Not Supported?

Hi,

Williams, Joshua a écrit :

> I have been trying to run the following query on an eXist DB Collection, 
> and it always returns 0 results (does not throw errors, just doesn't 
> return anything).  I run the same query on Oracle's Berkeley DB and it 
> returns the appropriate number of results.  Is something about the query 
> not supported in eXist?

You have hit a well-known bug in the evaluation of where clauses where 
anonymous nodes can not be properly resolved.

Specify the node's name :

for $x in collection("/db")/AllElements
where 
$x/Element/SubElementA[.='Value1A']/parent::Element/SubElementB/Value[.='Value1B']
return $x

... or use a filtering expression (which is more in the XQuery spirit 
IMHO) :

for $x in 
collection("/db")/AllElements[Element/SubElementA[.='Value1A']/../SubElementB/Value[.='Value1B']]
return $x

Cheers,

--

-- 

Re: Need help understanding text searching

Many Thanks I think I now understand and know how to get everything to work.

By the way a few days ago I sent an e-mail subject: 'Something quite 
wrong on ResourceSet getResource (or removeResource) for index 0'
Though I was quite able to work around it by using the index 
(resset.getSize() - 1), might be good if somebody had a look and replied 
to it and said yes there is a bug there that needs to be fixed.

cheers,
Kevin

Michael Beddow wrote:
> Kevin Benson wrote:
>
>   
>> Now I ran tests and of course
>> match-all() and near() are much faster.
>>     
>
> "Of course" is true if you are using the default fulltext indexing settings
> and have no range indexes configured on the elements you are running
> matches() against. But with suitable range indexes to assist the matches()
> operator there needn't be much difference, though it does, as ever, depend
> somewhat on your data and your queries,
>
>   
>> near() does work and gives me correctly 2 results same as the longer
>> matches() query. Problem with near() is it does not seem to handle the
>> same expressions like match-all() and matches() unless there is
>> something I missed.

Re: XUpdate ArrayOutOfBoundsException