Fix some problems similar to #2832, but caused by triggers instead of an OR REPLACE clause. (CVS 4615)

FossilOrigin-Name: ee98ae17187296f7b0181c3d4d2b942d5cd4bc8f
This commit is contained in:
danielk1977
2007-12-12 16:06:23 +00:00
parent 2d78617d66
commit 967573d56a
5 changed files with 47 additions and 16 deletions
+34 -3
View File
@@ -11,13 +11,13 @@
#
# This file is to test that ticket #2832 has been fixed.
#
# $Id: tkt2832.test,v 1.1 2007/12/12 14:46:58 danielk1977 Exp $
# $Id: tkt2832.test,v 1.2 2007/12/12 16:06:23 danielk1977 Exp $
#
set testdir [file dirname $argv0]
source $testdir/tester.tcl
do_test tkt2832-2.1 {
do_test tkt2832-1.1 {
execsql {
CREATE TABLE t1(a PRIMARY KEY);
INSERT INTO t1 VALUES(2);
@@ -25,12 +25,43 @@ do_test tkt2832-2.1 {
INSERT INTO t1 VALUES(3);
}
} {}
do_test tkt2832-2.2 {
do_test tkt2832-1.2 {
execsql {
UPDATE OR REPLACE t1 SET a = 1;
SELECT * FROM t1;
}
} {1}
do_test tkt2832-2.1 {
execsql {
CREATE TABLE t2(a, b);
CREATE TRIGGER t2_t AFTER UPDATE ON t2 BEGIN
DELETE FROM t2 WHERE a = new.a + 1;
END;
INSERT INTO t2 VALUES(1, 2);
INSERT INTO t2 VALUES(2, 3);
}
} {}
do_test tkt2832-2.2 {
execsql {
UPDATE t2 SET b = 5
}
} {}
do_test tkt2832-3.1 {
execsql {
CREATE TABLE t3(a, b);
CREATE TRIGGER t3_t AFTER DELETE ON t3 BEGIN
DELETE FROM t3 WHERE a = old.a + 1;
END;
INSERT INTO t3 VALUES(1, 2);
INSERT INTO t3 VALUES(2, 3);
}
} {}
do_test tkt2832-3.2 {
explain { DELETE FROM t3 WHERE 1 }
execsql { DELETE FROM t3 WHERE 1 }
} {}
finish_test