Changes

Jump to navigation Jump to search
27 bytes removed ,  14:28, 16 May 2012
m
no edit summary
the <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
&quot;foo&quot; “foo” and the text node &quot;foo bar&quot;“foo bar”, and one error between&quot;foo&quot; “foo” and &quot;foa bar&quot;“foa bar”.
==Mixed Content==
</pre>
Since the logical flow of the text is not interrupted by the child elements, you will typically want to search across elements, so that the above paragraph would match a search for <code>real text</code>“real text”. For more examples, see [http://www.w3.org/TR/xpath-full-text-10-use-cases/#Across XQuery and XPath Full Text 1.0 Use Cases].
To enable this kind of searches, ''whitespace chopping'' must be turned off when importing XML documents by setting the option <code>[[Options#CHOP|CHOP]]</code> to <code>OFF</code> (default: <code>SET CHOP ON</code>). In the GUI, you find this option in Database → New… → Parsing → Chop Whitespaces.
</pre>
The ignore option would enable you to search for <code>illustrative purposes</code>the string “illustrative purposes”:
<pre class="brush:xquery">
editor, reviewer
10

edits

Navigation menu