Re: [Exist-open] Overview of eXist search functions / operators

[Ron V. d. B. <ron...@ka...>]

Hi,

Op 15/07/2010 11:19, Adam Retter schreef:
> Good idea, I think the only thing missing is the new qname value index...
>    

I'm not sure what you mean exactly, Adam. If I understand correctly, the 
qname index is a mechanism that can be applied to different index types 
(legacy FT, lucene FT, range) for identifying the elements/attributes to 
be indexed directly by specifying their name in a @qname attribute, as 
opposed to the context-dependent mechanism using the @path attribute on 
the respective index definitions. Or did I miss something, and is the 
qname index another index type from those mentioned in the overview at 
<http://demo.exist-db.org/exist/indexing.xml#N100F7>?

Related to this distinction, am I right in assuming that currently, the 
context-dependent index configuration is the only way to have eXist 
index all elements in a collection, like e.g.:
<lucene>
|<||text| |match=||"/PLAY/*"||/>|
</lucene>

(assuming PLAY is the root element of all documents). Also, when you 
want to index an element with all descendants, there seems to be no 
alternative but the (deprecated) context-dependent index configuration 
using @path, is there?

Which brings me to my final point of confusion: is it @path or @match 
(or both) for the context-dependent index configuration? Apparently, the 
Lucene FT index uses @match (as in above example -- see 
<http://demo.exist-db.org/exist/lucene.xml#N10203>), while all other 
index types (legacy FT, range) use @path (see 
<http://demo.exist-db.org/exist/indexing.xml>).

Finally, if such an overview could be of any value for the eXist 
documentation, I'd gladly contribute it, if someone can advice me on the 
preferred procedure and format.

Kind regards,

Ron

PS: apparently, I first misplaced the Wikibook page; it is now relocated 
at 
<http://en.wikibooks.org/wiki/XQuery/Overview_of_eXist_search_functions_and_operators>