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

third_party/sqlite/src/test/e_delete.test

 # 2010 September 21
 #
 # The author disclaims copyright to this source code.  In place of
 # a legal notice, here is a blessing:
 #
 #    May you do good and not evil.
 #    May you find forgiveness for yourself and forgive others.
 #    May you share freely, never taking more than you give.
 #
 #***********************************************************************
 #
 # This file implements tests to verify that the "testable statements" in 
 # the lang_delete.html document are correct.
 #
 set testdir [file dirname $argv0]
 source $testdir/tester.tcl
 
+ifcapable !compound {
+  finish_test
+  return
+}
+
 proc do_delete_tests {args} {
   uplevel do_select_tests $args
 }
 
 do_execsql_test e_delete-0.0 {
   CREATE TABLE t1(a, b);
   CREATE INDEX i1 ON t1(a);
 } {}
 
-# EVIDENCE-OF: R-24177-52883 -- syntax diagram delete-stmt
-#
-# EVIDENCE-OF: R-12802-60464 -- syntax diagram qualified-table-name
+# -- syntax diagram delete-stmt
+# -- syntax diagram qualified-table-name
 #
 do_delete_tests e_delete-0.1 {
   1  "DELETE FROM t1"                              {}
   2  "DELETE FROM t1 INDEXED BY i1"                {}
   3  "DELETE FROM t1 NOT INDEXED"                  {}
   4  "DELETE FROM main.t1"                         {}
   5  "DELETE FROM main.t1 INDEXED BY i1"           {}
   6  "DELETE FROM main.t1 NOT INDEXED"             {}
   7  "DELETE FROM t1 WHERE a>2"                    {}
   8  "DELETE FROM t1 INDEXED BY i1 WHERE a>2"      {}
@@ skipping 240 matching lines @@
       DELETE FROM t8 ORDER BY a LIMIT 5;
     END;
   } {ORDER}
 }
 
 # EVIDENCE-OF: R-40026-10531 If SQLite is compiled with the
 # SQLITE_ENABLE_UPDATE_DELETE_LIMIT compile-time option, then the syntax
 # of the DELETE statement is extended by the addition of optional ORDER
 # BY and LIMIT clauses:
 #
-# EVIDENCE-OF: R-45897-01670 -- syntax diagram delete-stmt-limited
+# -- syntax diagram delete-stmt-limited
 #
 do_delete_tests e_delete-3.1 {
   1   "DELETE FROM t1 LIMIT 5"                                    {}
   2   "DELETE FROM t1 LIMIT 5-1 OFFSET 2+2"                       {}
   3   "DELETE FROM t1 LIMIT 2+2, 16/4"                            {}
   4   "DELETE FROM t1 ORDER BY x LIMIT 5"                         {}
   5   "DELETE FROM t1 ORDER BY x LIMIT 5-1 OFFSET 2+2"            {}
   6   "DELETE FROM t1 ORDER BY x LIMIT 2+2, 16/4"                 {}
   7   "DELETE FROM t1 WHERE x>2 LIMIT 5"                          {}
   8   "DELETE FROM t1 WHERE x>2 LIMIT 5-1 OFFSET 2+2"             {}
@@ skipping 132 matching lines @@
   SELECT a FROM t1
 } {
   1   "DELETE FROM t1 LIMIT 2"               {3 4 5}
   2   "DELETE FROM t1 LIMIT 3"               {4 5}
   3   "DELETE FROM t1 LIMIT 1 OFFSET 0"      {2 3 4 5}
   4   "DELETE FROM t1 LIMIT 1 OFFSET 1"      {1 3 4 5}
   5   "DELETE FROM t1 LIMIT 1 OFFSET 2"      {1 2 4 5}
 }
 
 
-# EVIDENCE-OF: R-26627-30313 The ORDER BY clause on an DELETE statement
+# EVIDENCE-OF: R-07548-13422 The ORDER BY clause on a DELETE statement
 # is used only to determine which rows fall within the LIMIT. The order
 # in which rows are deleted is arbitrary and is not influenced by the
 # ORDER BY clause.
 #
 #     In practice, rows are always deleted in rowid order.
 #
 do_delete_tests e_delete-3.10 -repair {
   rebuild_t1 
   catchsql { DROP TABLE t1log }
   execsql {
     CREATE TABLE t1log(x);
     CREATE TRIGGER tr1 AFTER DELETE ON t1 BEGIN
       INSERT INTO t1log VALUES(old.a);
     END;
   }
 } -query {
   SELECT x FROM t1log
 } {
   1   "DELETE FROM t1 ORDER BY a DESC LIMIT 2"   {4 5}
   2   "DELETE FROM t1 ORDER BY a DESC LIMIT -1"  {1 2 3 4 5}
   3   "DELETE FROM t1 ORDER BY a ASC LIMIT 2"    {1 2}
   4   "DELETE FROM t1 ORDER BY a ASC LIMIT -1"   {1 2 3 4 5}
 }
 
 }
  
 finish_test