Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix a couple of bugs in the examples in fts3.in. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
9bd28d637b2732eb2dc6bf130c7658fd |
User & Date: | dan 2009-12-01 14:27:21.000 |
Context
2009-12-01
| ||
15:30 | Fix two more typos in examples in fts3.in. (check-in: d075300786 user: dan tags: trunk) | |
14:27 | Fix a couple of bugs in the examples in fts3.in. (check-in: 9bd28d637b user: dan tags: trunk) | |
2009-11-30
| ||
15:37 | Clarify authorship of the original FTS3 code in fts3.html. (check-in: daf96c0053 user: dan tags: trunk) | |
Changes
Changes to pages/fts3.in.
︙ | ︙ | |||
173 174 175 176 177 178 179 | <i>-- Insert a row and allow FTS3 to assign a docid value using the same algorithm as</i> <i>-- SQLite uses for ordinary tables. In this case the new docid will be 54,</i> <i>-- one greater than the largest docid currently present in the table.</i> INSERT INTO pages(title, body) VALUES('Download', 'All SQLite source code...'); <i>-- Change the title of the row just inserted.</i> | | | 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 | <i>-- Insert a row and allow FTS3 to assign a docid value using the same algorithm as</i> <i>-- SQLite uses for ordinary tables. In this case the new docid will be 54,</i> <i>-- one greater than the largest docid currently present in the table.</i> INSERT INTO pages(title, body) VALUES('Download', 'All SQLite source code...'); <i>-- Change the title of the row just inserted.</i> UPDATE pages SET title = 'Download SQLite' WHERE rowid = 54; <i>-- Delete the entire table contents.</i> DELETE FROM pages; <i>-- The following is an error. It is not possible to assign non-NULL values to both</i> <i>-- the rowid and docid columns of an FTS3 table.</i> INSERT INTO pages(rowid, docid, title, body) VALUES(1, 2, 'A title', 'A document body'); |
︙ | ︙ | |||
653 654 655 656 657 658 659 | SELECT * FROM docs WHERE docs MATCH 'database sqlite'; <i>-- Query for the set of documents that contains either "sqlite" or "database".</i> <i>-- All three documents in the database are matched by this query.</i> SELECT * FROM docs WHERE docs MATCH 'sqlite OR database'; <i>-- Query for all documents that contain the term "database", but do not contain</i> | | | 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 | SELECT * FROM docs WHERE docs MATCH 'database sqlite'; <i>-- Query for the set of documents that contains either "sqlite" or "database".</i> <i>-- All three documents in the database are matched by this query.</i> SELECT * FROM docs WHERE docs MATCH 'sqlite OR database'; <i>-- Query for all documents that contain the term "database", but do not contain</i> <i>-- the term "sqlite". Document 1 is the only document that matches this criteria.</i> SELECT * FROM docs WHERE docs MATCH 'database NOT sqlite'; <i>-- The following query matches no documents. Because "and" is in lowercase letters,</i> <i>-- it is interpreted as a basic term query instead of an operator. Operators must</i> <i>-- be specified using capital letters. In practice, this query will match any documents</i> <i>-- that contain each of the three terms "database", "and" and "sqlite" at least once.</i> <i>-- No documents in the example data above match this criteria.</i> |
︙ | ︙ |