Documentation Source Text

Check-in [b5b65a3c13]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Change "the following three queries" to "the following four queries" in fts5.in.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: b5b65a3c1312fadb12933c8b1dc549870aa44a610dbc34e69a7e358658ca055c
User & Date: dan 2019-02-18 15:33:50.195
Context
2019-02-18
20:35
Fix typos in the fileformat2.html page. (check-in: eecca5ae5e user: drh tags: trunk)
15:33
Change "the following three queries" to "the following four queries" in fts5.in. (check-in: b5b65a3c13 user: dan tags: trunk)
15:22
Clarification of the StrAppend() routine in althttpd.c. (check-in: 90fe325e31 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/fts5.in.
︙︙
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231

<h2 tags="FTS5 Phrases">FTS5 Phrases</h2>
<p>
FTS queries are made up of <b>phrases</b>. A phrase is an ordered list of 
one or more tokens. A string is transformed into a phrase by passing it to
the FTS table tokenizer. Two phrases can be concatenated into a single 
large phrase using the "+" operator. For example, assuming the tokenizer
module being used tokenizes the input "one.two.three" to three separate
tokens, the following three queries all specify the same phrase:

<codeblock>
  ... MATCH '"one two three"'
  ... MATCH 'one + two + three'
  ... MATCH '"one two" + three'
  ... MATCH 'one.two.three'
</codeblock>








|








217
218
219
220
221
222
223
224
225
226
227
228
229
230
231

<h2 tags="FTS5 Phrases">FTS5 Phrases</h2>
<p>
FTS queries are made up of <b>phrases</b>. A phrase is an ordered list of 
one or more tokens. A string is transformed into a phrase by passing it to
the FTS table tokenizer. Two phrases can be concatenated into a single 
large phrase using the "+" operator. For example, assuming the tokenizer
module being used tokenizes the input "one.two.three" to three separate
tokens, the following four queries all specify the same phrase:

<codeblock>
  ... MATCH '"one two three"'
  ... MATCH 'one + two + three'
  ... MATCH '"one two" + three'
  ... MATCH 'one.two.three'
</codeblock>
︙︙