Make sure my recent changes are represented in the patches....

third_party/sqlite/README.chromium

 Instructions for importing a new release of SQLite from sqlite.org.
 
 Note: our current base version is 3.6.18.
 
 First, you need to be on Linux.
 
 # Determine the versions of the release you want and the release we currently
 # have. (See the VERSION file to determine which release we currently have.)
 # You may wish to consult http://www.sqlite.org/changes.html to find out what
 # changes have been made in each release.
@@ skipping 35 matching lines @@
 
 For reference, all of our local patches are also kept as .patch files in the
 sqlite directory. Here is a list of the patches, in the order they should be
 applied to a vanilla SQLite (of the version we currently have) to get, in
 principle, exactly what is checked in:
 
 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:
 
 cd sqlite-$LATEST
 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!
 
 Descriptions of the changes we've made can be found at the bottom of this file.
 
 --------------------------------------------
 
 How to run the SQLite tests for the Chromium version of SQLite on Linux.
 
@@ skipping 12 matching lines @@
 # However, the current situation on my corp Linux Ubuntu 8.04 machine, with
 # test run on a locally mounted directory, is the failure of:
 # "rollback-2.3", "tkt3457-1.4"
 # I do not know why, but it is not related to our fts2.c changes -- I backed
 # them out to check.
 
 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.
  - Tweak to SQLITE_EXTENSION_INIT* in sqlite3ext.h.
    - That implied a change in src/test_autoext.c for testing.
  - Added fts.test and fts1.test in tests, modified quick.test.
  - src/os_symbian.cc.
  - Modifications to Makefile.linux-gcc and main.mk for compiling
    SQLite tests.
  - Compile warning (cast to void* for sqlite3_free) fixed in func.c.
@@ skipping 25 matching lines @@
    allows much faster performance by reading the file in one contiguous
    operation rather than bringing it in organically, which involves a lot of
    seeking. This change also required sqlite3PcacheGetCachesize to be compiled
    even outside SQLITE_TEST.
  - Added a new function chromium_sqlite3_initialize_win_sqlite3_file()
    at the end of os_win.c. It allows the Windows-specific Chromium VFS
    to reuse most of the win32 SQLite VFS.
  - Added a new function initUnixFile() and made fillInUnixFile()
    non-static in os_unix.c. It allows the Linux-specific Chromium VFS
    to reuse most of the unix SQLite VFS.