Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
History for test/fts2k.test
2023-06-07
| ||
15:00 | Deleted: Remove additional traces of FTS1 and FTS2 that were missed by [2bb50d5aedef0fd2] (check-in: [9a12bac5d2] user: drh branch: trunk, size: 0) | |
2007-08-10
| ||
23:47 |
[c7ebf4a493]
part of check-in [16730cb137]
Convert fts2 to use sqlite3_prepare_v2() to prevent certain logic
errors around SQLITE_SCHEMA handling. This also allows
sql_step_statement() and sql_step_leaf_statement() to be replaced with
sqlite3_step().
Also fix a logic error in flushPendingTerms() which was clearing the term table in case of error. This was wrong in the face of SQLITE_SCHEMA. Even though the change to sqlite3_prepare_v2() should cause us not to see SQLITE_SCHEMA any longer, it was still a logic error... (CVS 4205) (check-in: [16730cb137] user: shess branch: trunk, size: 2852) | |
2007-03-29
| ||
18:41 | Added: [222d0b3bc8] part of check-in [0229cba696] Buffer updates per-transaction rather than per-update. If lots of updates happen within a single transaction, there was a lot of wasted encode/decode overhead due to segment merges. This code buffers updates in memory and writes out larger level-0 segments. It only works when documents are presented in ascending order by docid. Comparing a test set running 100 documents per transaction, the total runtime is cut almost in half. (CVS 3751) (check-in: [0229cba696] user: shess branch: trunk, size: 2299) | |