Changes

* With the {{Code|stop words}} option, a list of words can be defined that will be ignored when tokenizing a string. This is particularly helpful when the size of a full-text index structure needs to be reducedtakes too much space:

The available full[[Indexes#Full-Text Index|Full-text index Text Index]] can handle various combinations of the match options defined in the XQuery Full Text Recommendation. By default, most options are disabled. The GUI dialogs for creating new databases or displaying the database properties contain a tab for choosing between all available options. On the command-line, the <code>SET</code> command can be used to activate full-text indexing or creating a full-text index for existing databases:

BaseX supports full-text queries using thesauri, but it does not provide a default thesaurus. This is why queries such as:

In addition to the official recommendation, BaseX supports a fuzzy queryingsearch feature.The XQFT grammar was enhanced by the FTMatchOption <code>using fuzzy </code> to allow for approximate searches results in full texts.By default, Fuzzy search is also supported by the standard [[indexesIndexes#Full-Text Index|fullFull-text indexText Index]] already supports the efficientexecution of fuzzy searches.

Fuzzy search is based on the Levenshtein distance. The maximum number of allowederrors is calculated by dividing the token length of a specified query term by 4,preserving a minimum of 1 errors. A static error distance can be set by adjustingthe <code>[[Options#LSERROR|LSERROR]]</code> property (default: <code>SET LSERROR 0</code>).The query above yields two results as there is no error between the query term“house” and the text node “house”, and one error between“house” and “hous”.