Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix an error in the FTS matchinfo documentation. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
4a7f0dacc7e3598943d4470f081110b4 |
| User & Date: | dan 2012-02-05 05:19:56 |
Context
|
2012-02-23
| ||
| 12:32 | Fix a typo in the lang_keywords.html page. (check-in: f8a77cd24f user: drh tags: trunk) | |
|
2012-02-05
| ||
| 05:19 | Fix an error in the FTS matchinfo documentation. (check-in: 4a7f0dacc7 user: dan tags: trunk) | |
|
2012-01-28
| ||
| 19:47 | Update the changelog to mention IF NOT EXISTS on virtual tables. (check-in: b0db418b5a user: drh tags: trunk) | |
Changes
Changes to pages/fts3.in.
1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 |
<i>--</i> <i>-- The next set of three integers (0 1 1) pertain to the hits for "default"</i> <i>-- in column 1 of the table (0 in this row, 1 in all rows, spread across </i> <i>-- 1 rows).</i> <i>--</i> SELECT matchinfo(t1) FROM t1 WHERE t1 MATCH 'default transaction "these semantics"'; <i>-- The format string for this query is "nl". The output array will therefore</i> <i>-- contain 3 integer values - 1 for "n" and 2 for "l". The query returns</i> <i>-- two rows (the first two rows in the table match). The values returned are:</i> <i>--</i> <i>-- 3 1 1</i> <i>-- 3 2 0</i> <i>--</i> <i>-- The first value in the matchinfo array returned for both rows is 3 (the </i> <i>-- number of rows in the table). The following two values are the lengths </i> <i>-- of the longest common subsequence of phrase matches in each column.</i> SELECT matchinfo(t1, 'nl') FROM t1 WHERE t1 MATCH 'default transaction'; </codeblock> <p> The matchinfo function is much faster than either the snippet or offsets functions. This is because the implementation of both snippet and offsets is required to retrieve the documents being analyzed from disk, whereas all data required by matchinfo is available as part of the same portions |
| | | |
1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 |
<i>--</i> <i>-- The next set of three integers (0 1 1) pertain to the hits for "default"</i> <i>-- in column 1 of the table (0 in this row, 1 in all rows, spread across </i> <i>-- 1 rows).</i> <i>--</i> SELECT matchinfo(t1) FROM t1 WHERE t1 MATCH 'default transaction "these semantics"'; <i>-- The format string for this query is "ns". The output array will therefore</i> <i>-- contain 3 integer values - 1 for "n" and 2 for "s". The query returns</i> <i>-- two rows (the first two rows in the table match). The values returned are:</i> <i>--</i> <i>-- 3 1 1</i> <i>-- 3 2 0</i> <i>--</i> <i>-- The first value in the matchinfo array returned for both rows is 3 (the </i> <i>-- number of rows in the table). The following two values are the lengths </i> <i>-- of the longest common subsequence of phrase matches in each column.</i> SELECT matchinfo(t1, 'ns') FROM t1 WHERE t1 MATCH 'default transaction'; </codeblock> <p> The matchinfo function is much faster than either the snippet or offsets functions. This is because the implementation of both snippet and offsets is required to retrieve the documents being analyzed from disk, whereas all data required by matchinfo is available as part of the same portions |