Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Do not require SQLITE_ENABLE_BROKEN_FTS2 if FTS2 is not enabled. The same for FTS1. Ticket #2777. (CVS 4556) |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
f94cdcfd1171fd110ed9cd4c47f1fb5f |
User & Date: | drh 2007-11-23 18:06:23.000 |
Context
2007-11-23
| ||
18:19 | Fix a typo in a change to all.test from earlier today. (CVS 4557) (check-in: 8c0b2157f2 user: drh tags: trunk) | |
18:06 | Do not require SQLITE_ENABLE_BROKEN_FTS2 if FTS2 is not enabled. The same for FTS1. Ticket #2777. (CVS 4556) (check-in: f94cdcfd11 user: drh tags: trunk) | |
18:01 | Add a #include of sqlite3.h to fts3_hash.c. Tickets #2762 and #2777. (CVS 4555) (check-in: c8485eb8bc user: drh tags: trunk) | |
Changes
Changes to ext/fts1/fts1.c.
1 2 3 4 5 | /* fts1 has a design flaw which can lead to database corruption (see ** below). It is recommended not to use it any longer, instead use ** fts3 (or higher). If you believe that your use of fts1 is safe, ** add -DSQLITE_ENABLE_BROKEN_FTS1=1 to your CFLAGS. */ | > | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | /* fts1 has a design flaw which can lead to database corruption (see ** below). It is recommended not to use it any longer, instead use ** fts3 (or higher). If you believe that your use of fts1 is safe, ** add -DSQLITE_ENABLE_BROKEN_FTS1=1 to your CFLAGS. */ #if (!defined(SQLITE_CORE) || defined(SQLITE_ENABLE_FTS1)) \ && !defined(SQLITE_ENABLE_BROKEN_FTS1) #error fts1 has a design flaw and has been deprecated. #endif /* The flaw is that fts1 uses the content table's unaliased rowid as ** the unique docid. fts1 embeds the rowid in the index it builds, ** and expects the rowid to not change. The SQLite VACUUM operation ** will renumber such rowids, thereby breaking fts1. If you are using ** fts1 in a system which has disabled VACUUM, then you can continue |
︙ | ︙ |
Changes to ext/fts2/fts2.c.
1 2 3 4 5 | /* fts2 has a design flaw which can lead to database corruption (see ** below). It is recommended not to use it any longer, instead use ** fts3 (or higher). If you believe that your use of fts2 is safe, ** add -DSQLITE_ENABLE_BROKEN_FTS2=1 to your CFLAGS. */ | > | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | /* fts2 has a design flaw which can lead to database corruption (see ** below). It is recommended not to use it any longer, instead use ** fts3 (or higher). If you believe that your use of fts2 is safe, ** add -DSQLITE_ENABLE_BROKEN_FTS2=1 to your CFLAGS. */ #if (!defined(SQLITE_CORE) || defined(SQLITE_ENABLE_FTS2)) \ && !defined(SQLITE_ENABLE_BROKEN_FTS2) #error fts2 has a design flaw and has been deprecated. #endif /* The flaw is that fts2 uses the content table's unaliased rowid as ** the unique docid. fts2 embeds the rowid in the index it builds, ** and expects the rowid to not change. The SQLite VACUUM operation ** will renumber such rowids, thereby breaking fts2. If you are using ** fts2 in a system which has disabled VACUUM, then you can continue |
︙ | ︙ |