Thanks Phil,

indeed I forgot to mention that all index full-text options, that have been chosen for index creation, must be specified in the XQuery as well; see this:

http://www.inf.uni-konstanz.de/dbis/basex/xquery.php#ftindex

We took this approach to be fully compliant with the xqft language extension - which, by default, does not activate any of the available match options.

Hope this helps, Christian

On Tue, Jan 12, 2010 at 12:04 AM, Phil Oliver phil3@olivercomputing.com wrote:

After some experimentation, I've identified the fulltext search index problem. Hopefully it's something easily fixed.

I did have the FT indexing turned on, but basically with all of the various options. I decided to experiment with the minimal index and then to systematically add options. It turns out that the query does use the FT index in the instance where there are no options, or with wildcards turned on. However, the index is no longer used once stemming, case sensitivity, or diacritics are turned on in the FT database indexing options.

The speed is impressive with the FT indexing enabled, I think good enough for me to plan to use it in development. However, the other FT options are potentially important (to me and others) and I hope it's a priority to fix the indexing problem.

Thanks for your help.

Phil

___________________________

Christian Gruen Universitaet Konstanz Department of Computer & Information Science D-78457 Konstanz, Germany Tel: +49 (0)7531/88-4449, Fax: +49 (0)7531/88-3577 http://www.inf.uni-konstanz.de/~gruen