summaryrefslogtreecommitdiffstats
path: root/third_party/sqlite/README.chromium
diff options
context:
space:
mode:
Diffstat (limited to 'third_party/sqlite/README.chromium')
-rw-r--r--third_party/sqlite/README.chromium6
1 files changed, 5 insertions, 1 deletions
diff --git a/third_party/sqlite/README.chromium b/third_party/sqlite/README.chromium
index 7262ff2..51a5927 100644
--- a/third_party/sqlite/README.chromium
+++ b/third_party/sqlite/README.chromium
@@ -53,6 +53,7 @@ misc.patch
preload-cache.patch
safe-tolower.patch
sqlite-poison.patch
+fts2.patch
So, e.g. you could do this to apply all our patches to vanilla SQLite:
@@ -61,6 +62,7 @@ patch -p0 < ../sqlite/misc.patch
patch -p0 < ../sqlite/preload-cache.patch
patch -p0 < ../sqlite/safe-tolower.patch
patch -p0 < ../sqlite/sqlite-poison.patch
+patch -p0 < ../sqlite/fts2.patch
This will only be the case if all changes we make also update the corresponding
patch files. Therefore please remember to do that whenever you make a change!
@@ -93,8 +95,10 @@ Chris Evans <cevans@google.com>, Oct 1, 2009
--------------------------------------------
-As of Sep 15, 2009, these are our changes from sqlite_vendor:
+As of Oct 1, 2009, these are our changes from sqlite_vendor:
+ - A large number of fts2 robustness fixes against corrupt data in its metadata
+ tables.
- fts2.c disables fts2_tokenizer().
- sqlite3Poison() in src/btree.c.
- BEGIN defaults to BEGIN IMMEDIATE in parse.y.