Documentation Source Text

Check-in [cc68da99a4]
Login

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

Overview
Comment:Fix typos in fts5.in.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: cc68da99a4030fecae0c70edfa15348ccadb49eb
User & Date: dan 2015-10-09 12:09:25
Context
2015-10-09
12:10
Fix one more typo in fts5.in. check-in: 1bbbec6248 user: dan tags: trunk
12:09
Fix typos in fts5.in. check-in: cc68da99a4 user: dan tags: trunk
2015-10-08
00:21
Minor English grammar changes. check-in: 543413f753 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/fts5.in.

37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
...
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
new table. These may be used to modify the way in which the FTS5 table extracts
terms from documents and queries, to create extra indexes on disk to speed up
prefix queries, or to create an FTS5 table that acts as an index on content
stored elsewhere.

<p>Once populated, a full-text query may be executed on the contents of an
FTS5 table by adding a MATCH constraint to the WHERE clause of a SELECT 
query. The expression to the right of the MATCH operator must be the name
of the FTS5 table. The expression on the left must be a text value specifying
the term to search for. For example: 

<codeblock>
  <i>-- Query for all rows that contain at least once instance of the term</i>
  <i>-- "fts5" (in any column).</i>
  SELECT * FROM email WHERE email MATCH 'fts5';
</codeblock>
................................................................................
if the "content_rowid" option is set within the CREATE VIRTUAL TABLE statement,
by the value of that option. &lt;cols&gt; is replaced by a comma-separated list
of the FTS5 table column names. For example:

<codeblock>
  <i>-- If the database schema is: </i>
  CREATE TABLE tbl (a, b, c, d INTEGER PRIMARY KEY);
  CREATE TABLE fts USING fts5(a, c, content=tbl, content_rowid=d);

  <i>-- Fts5 may issue queries such as:</i>
  SELECT d, a, c FROM tbl WHERE d = ?;
</codeblock>

<p> The content table may also be queried as follows:








|
|







 







|







37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
...
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
new table. These may be used to modify the way in which the FTS5 table extracts
terms from documents and queries, to create extra indexes on disk to speed up
prefix queries, or to create an FTS5 table that acts as an index on content
stored elsewhere.

<p>Once populated, a full-text query may be executed on the contents of an
FTS5 table by adding a MATCH constraint to the WHERE clause of a SELECT 
query. The expression to the left of the MATCH operator must be the name
of the FTS5 table. The expression on the right must be a text value specifying
the term to search for. For example: 

<codeblock>
  <i>-- Query for all rows that contain at least once instance of the term</i>
  <i>-- "fts5" (in any column).</i>
  SELECT * FROM email WHERE email MATCH 'fts5';
</codeblock>
................................................................................
if the "content_rowid" option is set within the CREATE VIRTUAL TABLE statement,
by the value of that option. &lt;cols&gt; is replaced by a comma-separated list
of the FTS5 table column names. For example:

<codeblock>
  <i>-- If the database schema is: </i>
  CREATE TABLE tbl (a, b, c, d INTEGER PRIMARY KEY);
  CREATE TABLE VIRTUAL fts USING fts5(a, c, content=tbl, content_rowid=d);

  <i>-- Fts5 may issue queries such as:</i>
  SELECT d, a, c FROM tbl WHERE d = ?;
</codeblock>

<p> The content table may also be queried as follows: