Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix the name in the documentation of the compile-time macro for enabling FTS3 parenthesis processing. (CVS 6089) |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
ac8258da6ecd3ea37f394dc3b48834eb |
| User & Date: | drh 2008-12-31 19:27:53 |
Context
|
2008-12-31
| ||
| 21:52 | Avoid surplus bytes at the end of the keyword string table. Add testcase() macros to make sure all keywords are used during testing. (CVS 6090) (check-in: 73958060 user: drh tags: trunk) | |
| 19:27 | Fix the name in the documentation of the compile-time macro for enabling FTS3 parenthesis processing. (CVS 6089) (check-in: ac8258da user: drh tags: trunk) | |
| 16:27 | Fix the FTS3 expression parser so that it works in the amalgamation when FTS3 is disabled. (CVS 6088) (check-in: 7e238e86 user: drh tags: trunk) | |
Changes
Changes to ext/fts3/README.syntax.
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
...
203
204
205
206
207
208
209
210
211
212
|
of the table. If it is set to a column name, then by default the query may only match the specified column. In both cases this may be overriden as part of the query text (see sections 2 and 3 below). As of SQLite version 3.6.8, Fts3 supports two slightly different query formats; the standard syntax, which is used by default, and the enhanced query syntax which can be selected by compiling with the pre-processor symbol SQLITE_FTS3_ENABLE_PARENTHESIS defined. -DSQLITE_FTS3_ENABLE_PARENTHESIS 2. STANDARD QUERY SYNTAX When using the standard Fts3 query syntax, a query usually consists of a list of terms (words) separated by white-space characters. To match a query, a row (or column) of an Fts3 table must contain each of the specified terms. For example, the following query: ................................................................................ tokens or phrases. Attempting the following query will return an error: <col> MATCH 'sqlite NEAR (fantastic OR impressive)' Queries of this form must be re-written as: <col> MATCH 'sqlite NEAR fantastic OR sqlite NEAR impressive' |
|
|
<
<
<
|
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
...
203
204
205
206
207
208
209
|
of the table. If it is set to a column name, then by default the query may only match the specified column. In both cases this may be overriden as part of the query text (see sections 2 and 3 below). As of SQLite version 3.6.8, Fts3 supports two slightly different query formats; the standard syntax, which is used by default, and the enhanced query syntax which can be selected by compiling with the pre-processor symbol SQLITE_ENABLE_FTS3_PARENTHESIS defined. -DSQLITE_ENABLE_FTS3_PARENTHESIS 2. STANDARD QUERY SYNTAX When using the standard Fts3 query syntax, a query usually consists of a list of terms (words) separated by white-space characters. To match a query, a row (or column) of an Fts3 table must contain each of the specified terms. For example, the following query: ................................................................................ tokens or phrases. Attempting the following query will return an error: <col> MATCH 'sqlite NEAR (fantastic OR impressive)' Queries of this form must be re-written as: <col> MATCH 'sqlite NEAR fantastic OR sqlite NEAR impressive' |