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

third_party/sqlite/src/test/trigger1.test

 # 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 tests creating and dropping triggers, and interaction thereof
 # with the database COMMIT/ROLLBACK logic.
 #
 # 1. CREATE and DROP TRIGGER tests
-# trig-1.1: Error if table does not exist
-# trig-1.2: Error if trigger already exists
-# trig-1.3: Created triggers are deleted if the transaction is rolled back
-# trig-1.4: DROP TRIGGER removes trigger
-# trig-1.5: Dropped triggers are restored if the transaction is rolled back
-# trig-1.6: Error if dropped trigger doesn't exist
-# trig-1.7: Dropping the table automatically drops all triggers
-# trig-1.8: A trigger created on a TEMP table is not inserted into sqlite_master
-# trig-1.9: Ensure that we cannot create a trigger on sqlite_master
-# trig-1.10:
-# trig-1.11:
-# trig-1.12: Ensure that INSTEAD OF triggers cannot be created on tables
-# trig-1.13: Ensure that AFTER triggers cannot be created on views
-# trig-1.14: Ensure that BEFORE triggers cannot be created on views
+# trigger1-1.1: Error if table does not exist
+# trigger1-1.2: Error if trigger already exists
+# trigger1-1.3: Created triggers are deleted if the transaction is rolled back
+# trigger1-1.4: DROP TRIGGER removes trigger
+# trigger1-1.5: Dropped triggers are restored if the transaction is rolled back
+# trigger1-1.6: Error if dropped trigger doesn't exist
+# trigger1-1.7: Dropping the table automatically drops all triggers
+# trigger1-1.8: A trigger created on a TEMP table is not inserted into sqlite_master
+# trigger1-1.9: Ensure that we cannot create a trigger on sqlite_master
+# trigger1-1.10:
+# trigger1-1.11:
+# trigger1-1.12: Ensure that INSTEAD OF triggers cannot be created on tables
+# trigger1-1.13: Ensure that AFTER triggers cannot be created on views
+# trigger1-1.14: Ensure that BEFORE triggers cannot be created on views
 #
 
 set testdir [file dirname $argv0]
 source $testdir/tester.tcl
-ifcapable {!trigger} {
+ifcapable !trigger||!compound {
   finish_test
   return
 }
 
 do_test trigger1-1.1.1 {
    catchsql {
      CREATE TRIGGER trig UPDATE ON no_such_table BEGIN
        SELECT * from sqlite_master;
      END;
    } 
@@ skipping 160 matching lines @@
 } {1 x-a 2 b 4 d}
 
 # Ensure that we cannot create INSTEAD OF triggers on tables
 do_test trigger1-1.12 {
   catchsql {
     create table t1(a,b);
     create trigger t1t instead of update on t1 for each row begin
       delete from t1 WHERE a=old.a+2;
     end;
   }
-} {1 {cannot create INSTEAD OF trigger on table: main.t1}}
+} {1 {cannot create INSTEAD OF trigger on table: t1}}
 
 ifcapable view {
 # Ensure that we cannot create BEFORE triggers on views
 do_test trigger1-1.13 {
   catchsql {
     create view v1 as select * from t1;
     create trigger v1t before update on v1 for each row begin
       delete from t1 WHERE a=old.a+2;
     end;
   }
-} {1 {cannot create BEFORE trigger on view: main.v1}}
+} {1 {cannot create BEFORE trigger on view: v1}}
 # Ensure that we cannot create AFTER triggers on views
 do_test trigger1-1.14 {
   catchsql {
     drop view v1;
     create view v1 as select * from t1;
     create trigger v1t AFTER update on v1 for each row begin
       delete from t1 WHERE a=old.a+2;
     end;
   }
-} {1 {cannot create AFTER trigger on view: main.v1}}
+} {1 {cannot create AFTER trigger on view: v1}}
 } ;# ifcapable view
 
 # Check for memory leaks in the trigger parser
 #
 do_test trigger1-2.1 {
   catchsql {
     CREATE TRIGGER r1 AFTER INSERT ON t1 BEGIN
       SELECT * FROM;  -- Syntax error
     END;
   }
@@ skipping 13 matching lines @@
   do_test trigger1-3.1 {
     execsql {
       CREATE TEMP TABLE t2(x,y);
     }
     catchsql {
       CREATE TRIGGER r1 AFTER INSERT ON t1 BEGIN
         INSERT INTO t2 VALUES(NEW.a,NEW.b);
       END;
     }
   } {0 {}}
-  do_test trigger-3.2 {
+  do_test trigger1-3.2 {
     catchsql {
       INSERT INTO t1 VALUES(1,2);
       SELECT * FROM t2;
     }
   } {1 {no such table: main.t2}}
-  do_test trigger-3.3 {
+  do_test trigger1-3.3 {
     db close
     set rc [catch {sqlite3 db test.db} err]
     if {$rc} {lappend rc $err}
     set rc
   } {0}
-  do_test trigger-3.4 {
+  do_test trigger1-3.4 {
     catchsql {
       INSERT INTO t1 VALUES(1,2);
       SELECT * FROM t2;
     }
   } {1 {no such table: main.t2}}
-  do_test trigger-3.5 {
+  do_test trigger1-3.5 {
     catchsql {
       CREATE TEMP TABLE t2(x,y);
       INSERT INTO t1 VALUES(1,2);
       SELECT * FROM t2;
     }
   } {1 {no such table: main.t2}}
-  do_test trigger-3.6 {
+  do_test trigger1-3.6.1 {
     catchsql {
       DROP TRIGGER r1;
       CREATE TEMP TRIGGER r1 AFTER INSERT ON t1 BEGIN
+        INSERT INTO t2 VALUES(NEW.a,NEW.b), (NEW.b*100, NEW.a*100);
+      END;
+      INSERT INTO t1 VALUES(1,2);
+      SELECT * FROM t2;
+    }
+  } {0 {1 2 200 100}}
+  do_test trigger1-3.6.2 {
+    catchsql {
+      DROP TRIGGER r1;
+      DELETE FROM t1;
+      DELETE FROM t2;
+      CREATE TEMP TRIGGER r1 AFTER INSERT ON t1 BEGIN
         INSERT INTO t2 VALUES(NEW.a,NEW.b);
       END;
       INSERT INTO t1 VALUES(1,2);
       SELECT * FROM t2;
     }
   } {0 {1 2}}
-  do_test trigger-3.7 {
+  do_test trigger1-3.7 {
     execsql {
       DROP TABLE t2;
       CREATE TABLE t2(x,y);
       SELECT * FROM t2;
     }
   } {}
 
-  # There are two versions of trigger-3.8 and trigger-3.9. One that uses
+  # There are two versions of trigger1-3.8 and trigger1-3.9. One that uses
   # compound SELECT statements, and another that does not.
   ifcapable compound {
   do_test trigger1-3.8 {
     execsql {
       INSERT INTO t1 VALUES(3,4);
       SELECT * FROM t1 UNION ALL SELECT * FROM t2;
     }
   } {1 2 3 4 3 4}
   do_test trigger1-3.9 {
     db close
@@ skipping 82 matching lines @@
   execsql {
     CREATE TRIGGER t2 BEFORE DELETE ON t2 BEGIN
       SELECT RAISE(ABORT,'deletes are not permitted');
     END;
     SELECT type, name FROM sqlite_master;
   }
 } [concat $view_v1 {table t2 trigger t2}]
 do_test trigger1-6.3 {
   catchsql {DELETE FROM t2}
 } {1 {deletes are not permitted}}
+verify_ex_errcode trigger1-6.3b SQLITE_CONSTRAINT_TRIGGER
 do_test trigger1-6.4 {
   execsql {SELECT * FROM t2}
 } {3 4 7 8}
 do_test trigger1-6.5 {
   db close
   sqlite3 db test.db
   execsql {SELECT type, name FROM sqlite_master}
 } [concat $view_v1 {table t2 trigger t2}]
 do_test trigger1-6.6 {
   execsql {
     DROP TRIGGER t2;
     SELECT type, name FROM sqlite_master;
   }
 } [concat $view_v1 {table t2}]
 do_test trigger1-6.7 {
   execsql {SELECT * FROM t2}
 } {3 4 7 8}
 do_test trigger1-6.8 {
   db close
   sqlite3 db test.db
   execsql {SELECT * FROM t2}
 } {3 4 7 8}
 
-integrity_check trigger-7.1
+integrity_check trigger1-7.1
 
 # Check to make sure the name of a trigger can be quoted so that keywords
 # can be used as trigger names.  Ticket #468
 #
 do_test trigger1-8.1 {
   execsql {
     CREATE TRIGGER 'trigger' AFTER INSERT ON t2 BEGIN SELECT 1; END;
     SELECT name FROM sqlite_master WHERE type='trigger';
   }
 } {trigger}
@@ skipping 24 matching lines @@
 do_test trigger1-8.6 {
   execsql {
     DROP TRIGGER [trigger];
     SELECT name FROM sqlite_master WHERE type='trigger';
   }
 } {}
 
 ifcapable conflict {
   # Make sure REPLACE works inside of triggers.
   #
-  # There are two versions of trigger-9.1 and trigger-9.2. One that uses
+  # There are two versions of trigger1-9.1 and trigger1-9.2. One that uses
   # compound SELECT statements, and another that does not.
   ifcapable compound {
     do_test trigger1-9.1 {
       execsql {
         CREATE TABLE t3(a,b);
         CREATE TABLE t4(x UNIQUE, b);
         CREATE TRIGGER r34 AFTER INSERT ON t3 BEGIN
           REPLACE INTO t4 VALUES(new.a,new.b);
         END;
         INSERT INTO t3 VALUES(1,2);
@@ skipping 34 matching lines @@
 
 # Ticket #764. At one stage TEMP triggers would fail to re-install when the
 # schema was reloaded. The following tests ensure that TEMP triggers are
 # correctly re-installed.
 #
 # Also verify that references within trigger programs are resolved at
 # statement compile time, not trigger installation time. This means, for
 # example, that you can drop and re-create tables referenced by triggers. 
 ifcapable tempdb&&attach {
   do_test trigger1-10.0 {
-    file delete -force test2.db
-    file delete -force test2.db-journal
+    forcedelete test2.db
+    forcedelete test2.db-journal
     execsql {
       ATTACH 'test2.db' AS aux;
     }
   } {}
   do_test trigger1-10.1 {
     execsql {
       CREATE TABLE main.t4(a, b, c);
       CREATE TABLE temp.t4(a, b, c);
       CREATE TABLE aux.t4(a, b, c);
       CREATE TABLE insert_log(db, a, b, c);
@@ skipping 44 matching lines @@
       INSERT INTO main.t4 VALUES(11, 12, 13);
       INSERT INTO temp.t4 VALUES(14, 15, 16);
       INSERT INTO aux.t4  VALUES(17, 18, 19);
     }
   } {}
   do_test trigger1-10.8 {
     execsql {
       SELECT * FROM insert_log;
     }
   } {main 11 12 13 temp 14 15 16 aux 17 18 19}
-  do_test trigger1-10.8 {
+  do_test trigger1-10.9 {
   # Drop and re-create the insert_log table in a different database. Note
   # that we can change the column names because the trigger programs don't
   # use them explicitly.
     execsql {
       DROP TABLE insert_log;
       CREATE TABLE aux.insert_log(db, d, e, f);
     }
   } {}
   do_test trigger1-10.10 {
     execsql {
@@ skipping 79 matching lines @@
 } {1 {the NOT INDEXED clause is not allowed on UPDATE or DELETE statements within triggers}}
 do_test trigger1-16.7 {
   catchsql {
     CREATE TRIGGER main.t16err7 AFTER INSERT ON tA BEGIN
       DELETE FROM t16 INDEXED BY t16a WHERE a=123;
     END;
   }
 } {1 {the INDEXED BY clause is not allowed on UPDATE or DELETE statements within triggers}}
 
 finish_test