Add //third_party/sqlite to dirs_to_snapshot, remove net_sql.patch

third_party/sqlite/src/test/where7.test

Index: third_party/sqlite/src/test/where7.test
diff --git a/third_party/sqlite/src/test/where7.test b/third_party/sqlite/src/test/where7.test
index e34778c76311f076a8f54da088090125c7b7a8a6..5032c698b217f691e018cad152fc032a7aee0fc2 100644
--- a/third_party/sqlite/src/test/where7.test
+++ b/third_party/sqlite/src/test/where7.test
@@ -10,8 +10,6 @@
 #***********************************************************************
 # This file implements regression tests for SQLite library.  The
 # focus of this file is testing the multi-index OR clause optimizer.
-#
-# $Id: where7.test,v 1.9 2009/06/07 23:45:11 drh Exp $
 
 set testdir [file dirname $argv0]
 source $testdir/tester.tcl
@@ -23305,7 +23303,7 @@ do_test where7-2.1001.2 {
 #
 # The test case that follows is code from an actual
 # application with identifiers change and unused columns
-# remove.
+# removed.
 #
 do_execsql_test where7-3.1 {
   CREATE TABLE t301 (
@@ -23334,16 +23332,16 @@ do_execsql_test where7-3.1 {
   
   EXPLAIN QUERY PLAN
   SELECT t302.c1 
-    FROM t302 JOIN t301 ON t302.c8 = t301.c8
+    FROM t302 JOIN t301 ON t302.c8 = +t301.c8
     WHERE t302.c2 = 19571
       AND t302.c3 > 1287603136
       AND (t301.c4 = 1407449685622784
            OR t301.c8 = 1407424651264000)
    ORDER BY t302.c5 LIMIT 200;
 } {
-  0 0 1 {SEARCH TABLE t301 USING COVERING INDEX t301_c4 (c4=?) (~10 rows)} 
-  0 0 1 {SEARCH TABLE t301 USING INTEGER PRIMARY KEY (rowid=?) (~1 rows)} 
-  0 1 0 {SEARCH TABLE t302 USING INDEX t302_c8_c3 (c8=? AND c3>?) (~2 rows)} 
+  0 0 1 {SEARCH TABLE t301 USING COVERING INDEX t301_c4 (c4=?)} 
+  0 0 1 {SEARCH TABLE t301 USING INTEGER PRIMARY KEY (rowid=?)} 
+  0 1 0 {SEARCH TABLE t302 USING INDEX t302_c8_c3 (c8=? AND c3>?)} 
   0 0 0 {USE TEMP B-TREE FOR ORDER BY}
 }