3 # The author disclaims copyright to this source code. In place of
4 # a legal notice, here is a blessing:
6 # May you do good and not evil.
7 # May you find forgiveness for yourself and forgive others.
8 # May you share freely, never taking more than you give.
10 #***********************************************************************
11 # This file implements regression tests for SQLite library. The
12 # focus of this file is testing the 'progress callback'.
14 # $Id: progress.test,v 1.8 2007/06/15 14:53:53 danielk1977 Exp $
16 set testdir [file dirname $argv0]
17 source $testdir/tester.tcl
19 # If the progress callback is not available in this build, skip this
26 # Build some test data
31 INSERT INTO t1 VALUES(1);
32 INSERT INTO t1 VALUES(2);
33 INSERT INTO t1 VALUES(3);
34 INSERT INTO t1 VALUES(4);
35 INSERT INTO t1 VALUES(5);
36 INSERT INTO t1 VALUES(6);
37 INSERT INTO t1 VALUES(7);
38 INSERT INTO t1 VALUES(8);
39 INSERT INTO t1 VALUES(9);
40 INSERT INTO t1 VALUES(10);
45 # Test that the progress callback is invoked.
46 do_test progress-1.0 {
48 db progress 1 "[namespace code {incr counter}] ; expr 0"
54 do_test progress-1.0.1 {
56 } {::namespace inscope :: {incr counter} ; expr 0}
57 do_test progress-1.0.2 {
58 set v [catch {db progress xyz bogus} msg]
60 } {1 {expected integer but got "xyz"}}
62 # Test that the query is abandoned when the progress callback returns non-zero
63 do_test progress-1.1 {
65 db progress 1 "[namespace code {incr counter}] ; expr 1"
66 set rc [catch {execsql {
72 # Test that the query is rolled back when the progress callback returns
74 do_test progress-1.2 {
76 # This figures out how many opcodes it takes to copy 5 extra rows into t1.
77 db progress 1 "[namespace code {incr five_rows}] ; expr 0"
80 INSERT INTO t1 SELECT a+10 FROM t1 WHERE a < 6
84 DELETE FROM t1 WHERE a > 10
87 # Now set up the progress callback to abandon the query after the number of
88 # opcodes to copy 5 rows. That way, when we try to copy 6 rows, we know
89 # some data will have been inserted into the table by the time the progress
90 # callback abandons the query.
91 db progress $five_rows "expr 1"
93 INSERT INTO t1 SELECT a+10 FROM t1 WHERE a < 9
96 SELECT count(*) FROM t1
100 # Test that an active transaction remains active and not rolled back
101 # after the progress query abandons a query.
103 # UPDATE: It is now recognised that this is a sure route to database
104 # corruption. So the transaction is rolled back.
105 do_test progress-1.3 {
110 INSERT INTO t1 VALUES(11)
112 db progress 1 "expr 1"
114 INSERT INTO t1 VALUES(12)
118 } {1 {cannot commit - no transaction is active}}
119 do_test progress-1.3.1 {
121 SELECT count(*) FROM t1
125 # Check that a value of 0 for N means no progress callback
126 do_test progress-1.4 {
128 db progress 0 "[namespace code {incr counter}] ; expr 0"
137 # Make sure other queries can be run from within the progress
138 # handler. Ticket #1827
140 do_test progress-1.5 {
144 set ::rx [db eval {SELECT count(*) FROM t1}]
147 db progress 10 set_rx
149 SELECT sum(a) FROM t1
152 do_test progress-1.6 {
156 # Check that abandoning a query using the progress handler does
157 # not cause other queries to abort. Ticket #2415.
158 do_test progress-1.7 {
160 CREATE TABLE abc(a, b, c);
161 INSERT INTO abc VALUES(1, 2, 3);
162 INSERT INTO abc VALUES(4, 5, 6);
163 INSERT INTO abc VALUES(7, 8, 9);
167 explain {SELECT a, b, c FROM abc}
168 db eval {SELECT a, b, c FROM abc} {
169 lappend ::res $a $b $c
170 db progress 5 "expr 1"
171 catch {db eval {SELECT a, b, c FROM abc} { }} msg
172 db progress 5 "expr 0"
177 } {1 2 3 interrupted 4 5 6 interrupted 7 8 9 interrupted}