Import SQLite 3.10.2.

third_party/sqlite/patches/0008-fts3-Interior-node-corruption-detection.patch

Index: third_party/sqlite/patches/0008-fts3-Interior-node-corruption-detection.patch
diff --git a/third_party/sqlite/patches/0009-fts3-Interior-node-corruption-detection.patch b/third_party/sqlite/patches/0008-fts3-Interior-node-corruption-detection.patch
similarity index 86%
rename from third_party/sqlite/patches/0009-fts3-Interior-node-corruption-detection.patch
rename to third_party/sqlite/patches/0008-fts3-Interior-node-corruption-detection.patch
index 99b17b855a588e16113f3acf67a02ddae0f131ef..69a628211b94e82bdc6e320ad79214393ac254b4 100644
--- a/third_party/sqlite/patches/0009-fts3-Interior-node-corruption-detection.patch
+++ b/third_party/sqlite/patches/0008-fts3-Interior-node-corruption-detection.patch
@@ -1,7 +1,7 @@
-From ce5e0e867ac54738b813c800cf1a0545258189bc Mon Sep 17 00:00:00 2001
+From 3141c2a626c531ba20ec54397a09fb6b88d07c4a Mon Sep 17 00:00:00 2001
 From: Scott Hess <shess@chromium.org>
 Date: Thu, 26 May 2011 18:44:46 +0000
-Subject: [PATCH 09/16] [fts3] Interior node corruption detection.
+Subject: [PATCH 08/10] [fts3] Interior node corruption detection.
 
 In auditing as part of a previous import, I noticed this case which
 seemed to allow for buffer overrun.  The nPrefix check was commented out
@@ -21,10 +21,10 @@ http://codereview.chromium.org/6990047 (3.7.6.3 SQLite import)
  1 file changed, 8 insertions(+), 2 deletions(-)
 
 diff --git a/third_party/sqlite/src/ext/fts3/fts3.c b/third_party/sqlite/src/ext/fts3/fts3.c
-index dbd2835..3a1152d 100644
+index 4f2ebb8..8f15099 100644
 --- a/third_party/sqlite/src/ext/fts3/fts3.c
 +++ b/third_party/sqlite/src/ext/fts3/fts3.c
-@@ -1773,8 +1773,14 @@ static int fts3ScanInteriorNode(
+@@ -1822,8 +1822,14 @@ static int fts3ScanInteriorNode(
      isFirstTerm = 0;
      zCsr += fts3GetVarint32(zCsr, &nSuffix);
      
@@ -42,5 +42,5 @@ index dbd2835..3a1152d 100644
      }
      if( nPrefix+nSuffix>nAlloc ){
 -- 
-2.2.1
+2.7.0