Documentation Source Text

Check-in [897b36953b]
Login

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

Overview
Comment:Fix typo in fts3.html.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 897b36953b643ce69a8695b629e7abb12a6bbe94
User & Date: dan 2010-01-20 05:52:41
Context
2010-01-20
18:32
Change the way the fts3.html document is generated to be more similar to most of the other documents. check-in: e3ae335670 user: dan tags: trunk
05:52
Fix typo in fts3.html. check-in: 897b36953b user: dan tags: trunk
2010-01-18
14:12
Add a section to fts3.in to explain how to use the matchinfo() function efficiently. check-in: 0917dec067 user: dan tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/fts3.in.

100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
  );
}]

<p>
  As well as a list of columns, the module arguments passed to a CREATE
  VIRTUAL TABLE statement used to create an FTS3 table may be used to specify
  a \[tokenizer\]. This is done by specifying a string of the form
  "tokenize=&lt;tokenizer name&gt; &lt;tokenizer args&lt;" in place of a column
  name, where &lt;tokenizer name&gt; is the name of the tokenizer to use and
  &lt;tokenizer args&gt; is an optional list of whitespace separated qualifiers
  to pass to the tokenizer implementation. A tokenizer specification may be
  placed anywhere in the column list, but at most one tokenizer declaration is
  allowed for each CREATE VIRTUAL TABLE statement.  The second and subsequent
  tokenizer declaration are interpreted as column names. 
  \[tokenizer|See below\] for a detailed description of using (and, if







|







100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
  );
}]

<p>
  As well as a list of columns, the module arguments passed to a CREATE
  VIRTUAL TABLE statement used to create an FTS3 table may be used to specify
  a \[tokenizer\]. This is done by specifying a string of the form
  "tokenize=&lt;tokenizer name&gt; &lt;tokenizer args&gt;" in place of a column
  name, where &lt;tokenizer name&gt; is the name of the tokenizer to use and
  &lt;tokenizer args&gt; is an optional list of whitespace separated qualifiers
  to pass to the tokenizer implementation. A tokenizer specification may be
  placed anywhere in the column list, but at most one tokenizer declaration is
  allowed for each CREATE VIRTUAL TABLE statement.  The second and subsequent
  tokenizer declaration are interpreted as column names. 
  \[tokenizer|See below\] for a detailed description of using (and, if