Full-Text - Revision history

CG: Text replacement - "syntaxhighlight" to "pre"

2023-12-01T16:38:40Z

Text replacement - "syntaxhighlight" to "pre"

CG: Text replacement - "" to "

2023-12-01T16:34:43Z

Text replacement - "<syntaxhighlight lang="xquery">" to "<pre lang='xquery'>"

Show changes

CG: Text replacement - "" to ""

2023-12-01T16:31:31Z

Text replacement - "</syntaxhighlight>" to "</pre>"

Show changes

CG: Text replacement - "db:pre(" to "db:get("

2022-07-20T11:34:20Z

Text replacement - "db:pre(" to "db:get("

CG at 08:56, 20 July 2022

2022-07-20T08:56:53Z

CG: Text replacement - "db:open" to "db:pre"

2022-07-19T18:54:40Z

Text replacement - "db:open" to "db:pre"

CG at 18:01, 18 July 2022

2022-07-18T18:01:57Z

CG at 18:01, 18 July 2022

2022-07-18T18:01:28Z

CG: /* Fuzzy Querying */

2022-04-25T08:41:03Z

Fuzzy Querying

CG at 11:47, 19 August 2021

2021-08-19T11:47:11Z

@@ Line 219: / Line 219: @@
 If a thesaurus is employed…
-<syntaxhighlight lang="xml">
+<pre lang="xml">
 <thesaurus xmlns="http://www.w3.org/2007/xqftts/thesaurus">
    <entry>
@@ Line 255: / Line 255: @@
 '''Document 'doc.xml'''':
-<syntaxhighlight lang="xml">
+<pre lang="xml">
 <doc>
     <a>house</a>
@@ Line 269: / Line 269: @@
 '''Result:'''
-<syntaxhighlight lang="xml">
+<pre lang="xml">
 <a>house</a>
 <a>hous</a>
@@ Line 286: / Line 286: @@
 When working with so-called narrative XML documents, such as HTML, [https://tei-c.org/ TEI], or [https://docbook.org/ DocBook] documents, you typically have ''mixed content'', i.e., elements containing a mix of text and markup, such as:
-<syntaxhighlight lang="xml">
+<pre lang="xml">
 <p>This is only an illustrative <hi>example</hi>, not a <q>real</q> text.</p>
 </pre>

@@ Line 203: / Line 203: @@
 return $s || ': ' || $n,
-for $n score $s in db:pre('factbook')//text()[. contains text 'orthodox']
+for $n score $s in db:get('factbook')//text()[. contains text 'orthodox']
 order by $s descending
 return $s || ': ' || $n
@@ Line 311: / Line 311: @@
 <syntaxhighlight lang="xquery">
-let $docs := db:pre('docs')
+let $docs := db:get('docs')
 return db:create(
    'index-db',

@@ Line 294: / Line 294: @@
 To enable this kind of searches, it is recommendable to:
-* Turn off ''whitespace chopping'' when importing XML documents. This can be done by setting {{Option|CHOP}} to <code>OFF</code>. This can also be done in the GUI if a new database is created (''Database'' → ''New…'' → ''Parsing'' → ''Chop Whitespaces'').
+* Keep ''whitespace stripping'' turned off when importing XML documents. This can be done by ensuring that {{Option|STRIPWS}} is disabled. This can also be done in the GUI if a new database is created (''Database'' → ''New…'' → ''Parsing'' → ''Strip Whitespaces'').
-* Turn off automatic indentation by assigning <code>indent=no</code> to the {{Option|SERIALIZER}} option.
+* Keep automatic indentation turned off. Ensure that the [[Serialization|serialization parameter]] {{Code|indent}} is set to {{Code|no}}.
-A query such as <code>//p[. contains text 'real text']</code> will then match the example paragraph above.  However, the full-text index will '''not''' be used in this query, so it may take a long time.  The full-text index would be used for the query <code>//p[text() contains text 'real text']</code>, but this query will not find the example paragraph, because the matching text is split over two text nodes.
+A query such as <code>//p[. contains text 'real text']</code> will then match the example paragraph above.  However, the full-text index will '''not''' be used in this query, so it may take a long time.  The full-text index would be used for the query <code>//p[text() contains text 'real text']</code>, but this query will not find the example paragraph because the matching text is split over two text nodes.
-Note that the node structure is ignored by the full-text tokenizer: The {{Code|contains text}} expression applies all full-text operations to the ''string value'' of its left operand. As a consequence, the <code>ft:mark</code> and <code>ft:extract</code> functions (see [[Full-Text Module|Full-Text Functions]]) will only yield useful results if they are applied to single text nodes, as the following example demonstrates:
+Note that the node structure is ignored by the full-text tokenizer: The {{Code|contains text}} expression applies all full-text operations to the ''string value'' of its left operand. As a consequence, the {{Function|Full-Text|ft:mark}} and {{Function|Full-Text|ft:extract}} functions will only yield useful results if they are applied to single text nodes, as the following example demonstrates:
 <syntaxhighlight lang="xquery">
@@ Line 308: / Line 308: @@
 </syntaxhighlight>
-BaseX does '''not''' support the ''ignore option'' (<code>without content</code>) of the [https://www.w3.org/TR/xpath-full-text-10/#ftignoreoption W3C XQuery Full Text 1.0] Recommendation. If you want to ignore descendant element content, such as footnotes or other material that does not belong to the same logical text flow, you can build a second database from and exclude all information you do not want to search for. See the following example (visit [[XQuery Update]] to learn more about updates):
+BaseX does '''not''' support the ''ignore option'' (<code>without content</code>) of the [https://www.w3.org/TR/xpath-full-text-10/#ftignoreoption W3C XQuery Full Text 1.0] Recommendation. If you want to ignore descendant element content, such as footnotes or other material that does not belong to the same logical text flow, you can build a second database from and exclude all information you want to avoid searching for. See the following example (visit [[XQuery Update]] to learn more about updates):
 <syntaxhighlight lang="xquery">

@@ Line 203: / Line 203: @@
 return $s || ': ' || $n,
-for $n score $s in db:open('factbook')//text()[. contains text 'orthodox']
+for $n score $s in db:pre('factbook')//text()[. contains text 'orthodox']
 order by $s descending
 return $s || ': ' || $n
@@ Line 311: / Line 311: @@
 <syntaxhighlight lang="xquery">
-let $docs := db:open('docs')
+let $docs := db:pre('docs')
 return db:create(
    'index-db',

@@ Line 193: / Line 193: @@
 </syntaxhighlight>
-Scoring is supported within full-text expressions, by {{Function||ft:search}}, and by simple predicate tests that can be rewritten to {{Function||ft:search}}:
+Scoring is supported within full-text expressions, by {{Function|Full-Text|ft:search}}, and by simple predicate tests that can be rewritten to {{Function|Full-Text|ft:search}}:
 <syntaxhighlight lang="xquery">

@@ Line 276: / Line 276: @@
 Fuzzy search is based on the Levenshtein distance. The maximum number of allowed errors is calculated by dividing the token length of a specified query term by 4. 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”.
-A user-defined value can be adjusted globally via the {{Option|LSERROR}} option or, since {{Version|9.6}}, via an additional argument:
+A user-defined value can be adjusted globally via the {{Option|LSERROR}} option or via an additional argument:
 <syntaxhighlight lang="xquery">