Tom Bradford is the one working on the full text indexer. You will have
to check with him to see what his time-frame is for delivery. As far as the
"contains", it is part of the XPath Query. Try:
http://www.zvon.org/xxl/XPathTutorial/General/examples.html
for a good introduction to XPath Queries. Also, check out the W3C XPath definition. My code is designed around attribute searching, not text. Maybe someone has a sample, I don't know what is available in the docs.
The contains() function will not be the place where full text searching is executed. Contains is a substring search function only, and is not meant for full text searching where stemming and case rolling are applied.
What likely will be the case is that I extend our XPath implementation to support a special full text searching function. Other DBs use an operator like ~ for full text searching, but I'd rather not deviate from the spec.
Likely, the initial usage scenario would be something like:
/root[child[search(.,"words")]]
Where everything is just implicitly ANDed. Eventually, I'll add explicit ANDing as well as ORing, NOT, etc...
The indexer and stemmer are done, it's just a matter of updating the XPath implementation.
-- Tom Bradford - http://www.tbradford.org Architect - XQRL (XQuery Engine) - http://www.xqrl.com Apache Xindice (XML Database) - http://xml.apache.org/xindice Labrador (Web Services Hub) - http://www.notdotnet.org/labrador
