Update sqlite to 3.7.3.

third_party/sqlite/README.chromium

 Name: SQLite
 License File: src/LICENSE
 URL: http://sqlite.org/
 
 Instructions for importing a new release of SQLite from sqlite.org.
 
-Note: our current base version is 3.6.18.
+Note: our current base version is 3.7.3.
 
 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.
 # Note - this is just an example. Always refer to the version above for our
 # real current version.
 # Set some variables to remember the versions, e.g.:
-BASE=3.6.18
-LATEST=3.6.22
+BASE=3.7.3
+LATEST=3.7.4
 
 # Get to the src/third_party directory in your Chromium client:
 cd src/third_party
 
 # Download the .tar.gz files for the releases:
 # (If the URL changes you might need to find the new one.)
 wget http://www.sqlite.org/sqlite-$BASE.tar.gz
 wget http://www.sqlite.org/sqlite-$LATEST.tar.gz
 
 # Extract the vanilla current and desired versions:
@@ skipping 27 matching lines @@
 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
 fts3.patch
-icu-regexp.patch
 attach-integer.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
 patch -p0 < ../sqlite/fts3.patch
-patch -p0 < ../sqlite/icu-regexp.patch
 patch -p0 < ../sqlite/attach-integer.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 17 matching lines @@
 # them out to check.
 
 Chris Evans <cevans@google.com>, Oct 1, 2009
 
 --------------------------------------------
 
 As of May 07, 2010, these are our changes from sqlite_vendor:
 
  - A fix for a crash passing an integer expression to ATTACH / DETACH. See
  attach-integer.patch
- - A fix for a crash mis-calling the REGEXP() function of the ICU extension.
- See icu-regexp.patch
  - A large number of fts2 robustness fixes against corrupt data in its metadata
    tables.
  - fts2.c disables fts2_tokenizer().
  - fts3.c disables fts3_tokenizer().
  - sqlite3Poison() in src/btree.c.
  - 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
@@ skipping 24 matching lines @@
  - fts2_icu.c and fts3_icu.c have a critical bug. U8_NEXT is used over
    a UTF-16 string. It's rep$ by U16_NEXT (jungshik)
  - Added a new function sqlite3Preload we use to prime the database cache. It
    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.