1# 2011 Mar 16 2# 3# The author disclaims copyright to this source code. In place of 4# a legal notice, here is a blessing: 5# 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. 9# 10#*********************************************************************** 11# 12# The focus of this file is testing the session module. 13# 14 15if {![info exists testdir]} { 16 set testdir [file join [file dirname [info script]] .. .. test] 17} 18source [file join [file dirname [info script]] session_common.tcl] 19source $testdir/tester.tcl 20 21set testprefix session2 22 23proc test_reset {} { 24 catch { db close } 25 catch { db2 close } 26 forcedelete test.db test.db2 27 sqlite3 db test.db 28 sqlite3 db2 test.db2 29} 30 31########################################################################## 32# End of proc definitions. Start of tests. 33########################################################################## 34 35test_reset 36do_execsql_test 1.0 { 37 CREATE TABLE t1(a PRIMARY KEY, b); 38 INSERT INTO t1 VALUES('i', 'one'); 39} 40do_iterator_test 1.1 t1 { 41 DELETE FROM t1 WHERE a = 'i'; 42 INSERT INTO t1 VALUES('ii', 'two'); 43} { 44 {DELETE t1 0 X. {t i t one} {}} 45 {INSERT t1 0 X. {} {t ii t two}} 46} 47do_iterator_test 1.2 t1 { 48 INSERT INTO t1 VALUES(1.5, 99.9) 49} { 50 {INSERT t1 0 X. {} {f 1.5 f 99.9}} 51} 52 53 54# Execute each of the following blocks of SQL on database [db1]. Collect 55# changes using a session object. Apply the resulting changeset to 56# database [db2]. Then check that the contents of the two databases are 57# identical. 58# 59 60set set_of_tests { 61 1 { INSERT INTO %T1% VALUES(1, 2) } 62 63 2 { 64 INSERT INTO %T2% VALUES(1, NULL); 65 INSERT INTO %T2% VALUES(2, NULL); 66 INSERT INTO %T2% VALUES(3, NULL); 67 DELETE FROM %T2% WHERE a = 2; 68 INSERT INTO %T2% VALUES(4, NULL); 69 UPDATE %T2% SET b=0 WHERE b=1; 70 } 71 72 3 { INSERT INTO %T3% SELECT *, NULL FROM %T2% } 73 74 4 { 75 INSERT INTO %T3% SELECT a||a, b||b, NULL FROM %T3%; 76 DELETE FROM %T3% WHERE rowid%2; 77 } 78 79 5 { UPDATE %T3% SET c = a||b } 80 81 6 { UPDATE %T1% SET a = 32 } 82 83 7 { 84 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 85 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 86 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 87 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 88 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 89 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 90 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 91 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 92 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 93 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 94 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 95 DELETE FROM %T1% WHERE (rowid%3)==0; 96 } 97 98 8 { 99 BEGIN; 100 INSERT INTO %T1% SELECT randomblob(32), randomblob(32) FROM %T1%; 101 ROLLBACK; 102 } 103 9 { 104 BEGIN; 105 UPDATE %T1% SET b = 'xxx'; 106 ROLLBACK; 107 } 108 10 { 109 BEGIN; 110 DELETE FROM %T1% WHERE 1; 111 ROLLBACK; 112 } 113 11 { 114 INSERT INTO %T1% VALUES(randomblob(21000), randomblob(0)); 115 INSERT INTO %T1% VALUES(1.5, 1.5); 116 INSERT INTO %T1% VALUES(4.56, -99.999999999999999999999); 117 } 118 12 { 119 INSERT INTO %T2% VALUES(NULL, NULL); 120 } 121 122 13 { 123 DELETE FROM %T1% WHERE 1; 124 125 -- Insert many rows with real primary keys. Enough to force the session 126 -- objects hash table to resize. 127 INSERT INTO %T1% VALUES(0.1, 0.1); 128 INSERT INTO %T1% SELECT a+0.1, b+0.1 FROM %T1%; 129 INSERT INTO %T1% SELECT a+0.2, b+0.2 FROM %T1%; 130 INSERT INTO %T1% SELECT a+0.4, b+0.4 FROM %T1%; 131 INSERT INTO %T1% SELECT a+0.8, b+0.8 FROM %T1%; 132 INSERT INTO %T1% SELECT a+1.6, b+1.6 FROM %T1%; 133 INSERT INTO %T1% SELECT a+3.2, b+3.2 FROM %T1%; 134 INSERT INTO %T1% SELECT a+6.4, b+6.4 FROM %T1%; 135 INSERT INTO %T1% SELECT a+12.8, b+12.8 FROM %T1%; 136 INSERT INTO %T1% SELECT a+25.6, b+25.6 FROM %T1%; 137 INSERT INTO %T1% SELECT a+51.2, b+51.2 FROM %T1%; 138 INSERT INTO %T1% SELECT a+102.4, b+102.4 FROM %T1%; 139 INSERT INTO %T1% SELECT a+204.8, b+204.8 FROM %T1%; 140 } 141 142 14 { 143 DELETE FROM %T1% WHERE 1; 144 } 145 146 15 { 147 INSERT INTO %T1% VALUES(1, 1); 148 INSERT INTO %T1% SELECT a+2, b+2 FROM %T1%; 149 INSERT INTO %T1% SELECT a+4, b+4 FROM %T1%; 150 INSERT INTO %T1% SELECT a+8, b+8 FROM %T1%; 151 INSERT INTO %T1% SELECT a+256, b+256 FROM %T1%; 152 } 153 154 16 { 155 INSERT INTO %T4% VALUES('abc', 'def'); 156 INSERT INTO %T4% VALUES('def', 'abc'); 157 } 158 17 { UPDATE %T4% SET b = 1 } 159 18 { DELETE FROM %T4% WHERE 1 } 160} 161 162test_reset 163do_common_sql { 164 CREATE TABLE t1(a PRIMARY KEY, b); 165 CREATE TABLE t2(a, b INTEGER PRIMARY KEY); 166 CREATE TABLE t3(a, b, c, PRIMARY KEY(a, b)); 167 CREATE TABLE t4(a, b, PRIMARY KEY(b, a)); 168} 169 170foreach {tn sql} [string map {%T1% t1 %T2% t2 %T3% t3 %T4% t4} $set_of_tests] { 171 do_then_apply_sql $sql 172 do_test 2.$tn { compare_db db db2 } {} 173} 174 175# The following block of tests is similar to the last, except that the 176# session object is recording changes made to an attached database. The 177# main database contains a table of the same name as the table being 178# modified within the attached db. 179# 180test_reset 181forcedelete test.db3 182sqlite3 db3 test.db3 183do_test 3.0 { 184 execsql { 185 ATTACH 'test.db3' AS 'aux'; 186 CREATE TABLE t1(a, b PRIMARY KEY); 187 CREATE TABLE t2(x, y, z); 188 CREATE TABLE t3(a); 189 190 CREATE TABLE aux.t1(a PRIMARY KEY, b); 191 CREATE TABLE aux.t2(a, b INTEGER PRIMARY KEY); 192 CREATE TABLE aux.t3(a, b, c, PRIMARY KEY(a, b)); 193 CREATE TABLE aux.t4(a, b, PRIMARY KEY(b, a)); 194 } 195 execsql { 196 CREATE TABLE t1(a PRIMARY KEY, b); 197 CREATE TABLE t2(a, b INTEGER PRIMARY KEY); 198 CREATE TABLE t3(a, b, c, PRIMARY KEY(a, b)); 199 CREATE TABLE t4(a, b, PRIMARY KEY(b, a)); 200 } db2 201} {} 202 203proc xTrace {args} { puts $args } 204 205foreach {tn sql} [ 206 string map {%T1% aux.t1 %T2% aux.t2 %T3% aux.t3 %T4% aux.t4} $set_of_tests 207] { 208 do_then_apply_sql $sql aux 209 do_test 3.$tn { compare_db db2 db3 } {} 210} 211catch {db3 close} 212 213 214#------------------------------------------------------------------------- 215# The following tests verify that NULL values in primary key columns are 216# handled correctly by the session module. 217# 218test_reset 219do_execsql_test 4.0 { 220 CREATE TABLE t1(a PRIMARY KEY); 221 CREATE TABLE t2(a, b, c, PRIMARY KEY(c, b)); 222 CREATE TABLE t3(a, b INTEGER PRIMARY KEY); 223} 224 225foreach {tn sql changeset} { 226 1 { 227 INSERT INTO t1 VALUES(123); 228 INSERT INTO t1 VALUES(NULL); 229 INSERT INTO t1 VALUES(456); 230 } { 231 {INSERT t1 0 X {} {i 456}} 232 {INSERT t1 0 X {} {i 123}} 233 } 234 235 2 { 236 UPDATE t1 SET a = NULL; 237 } { 238 {DELETE t1 0 X {i 456} {}} 239 {DELETE t1 0 X {i 123} {}} 240 } 241 242 3 { DELETE FROM t1 } { } 243 244 4 { 245 INSERT INTO t3 VALUES(NULL, NULL) 246 } { 247 {INSERT t3 0 .X {} {n {} i 1}} 248 } 249 250 5 { INSERT INTO t2 VALUES(1, 2, NULL) } { } 251 6 { INSERT INTO t2 VALUES(1, NULL, 3) } { } 252 7 { INSERT INTO t2 VALUES(1, NULL, NULL) } { } 253 8 { INSERT INTO t2 VALUES(1, 2, 3) } { {INSERT t2 0 .XX {} {i 1 i 2 i 3}} } 254 9 { DELETE FROM t2 WHERE 1 } { {DELETE t2 0 .XX {i 1 i 2 i 3} {}} } 255 256} { 257 do_iterator_test 4.$tn {t1 t2 t3} $sql $changeset 258} 259 260 261#------------------------------------------------------------------------- 262# Test that if NULL is passed to sqlite3session_attach(), all database 263# tables are attached to the session object. 264# 265test_reset 266do_execsql_test 5.0 { 267 CREATE TABLE t1(a PRIMARY KEY); 268 CREATE TABLE t2(x, y PRIMARY KEY); 269} 270 271foreach {tn sql changeset} { 272 1 { INSERT INTO t1 VALUES(35) } { {INSERT t1 0 X {} {i 35}} } 273 2 { INSERT INTO t2 VALUES(36, 37) } { {INSERT t2 0 .X {} {i 36 i 37}} } 274 3 { 275 DELETE FROM t1 WHERE 1; 276 UPDATE t2 SET x = 34; 277 } { 278 {UPDATE t2 0 .X {i 36 i 37} {i 34 {} {}}} 279 {DELETE t1 0 X {i 35} {}} 280 } 281} { 282 do_iterator_test 5.$tn * $sql $changeset 283} 284 285#------------------------------------------------------------------------- 286# The next block of tests verify that the "indirect" flag is set 287# correctly within changesets. The indirect flag is set for a change 288# if either of the following are true: 289# 290# * The sqlite3session_indirect() API has been used to set the session 291# indirect flag to true, or 292# * The change was made by a trigger. 293# 294# If the same row is updated more than once during a session, then the 295# change is considered indirect only if all changes meet the criteria 296# above. 297# 298test_reset 299db function indirect [list S indirect] 300 301do_execsql_test 6.0 { 302 CREATE TABLE t1(a PRIMARY KEY, b, c); 303 304 CREATE TABLE t2(x PRIMARY KEY, y); 305 CREATE TRIGGER AFTER INSERT ON t2 WHEN new.x%2 BEGIN 306 INSERT INTO t2 VALUES(new.x+1, NULL); 307 END; 308} 309 310do_iterator_test 6.1.1 * { 311 INSERT INTO t1 VALUES(1, 'one', 'i'); 312 SELECT indirect(1); 313 INSERT INTO t1 VALUES(2, 'two', 'ii'); 314 SELECT indirect(0); 315 INSERT INTO t1 VALUES(3, 'three', 'iii'); 316} { 317 {INSERT t1 0 X.. {} {i 1 t one t i}} 318 {INSERT t1 1 X.. {} {i 2 t two t ii}} 319 {INSERT t1 0 X.. {} {i 3 t three t iii}} 320} 321 322do_iterator_test 6.1.2 * { 323 SELECT indirect(1); 324 UPDATE t1 SET c = 'I' WHERE a = 1; 325 SELECT indirect(0); 326} { 327 {UPDATE t1 1 X.. {i 1 {} {} t i} {{} {} {} {} t I}} 328} 329do_iterator_test 6.1.3 * { 330 SELECT indirect(1); 331 UPDATE t1 SET c = '.' WHERE a = 1; 332 SELECT indirect(0); 333 UPDATE t1 SET c = 'o' WHERE a = 1; 334} { 335 {UPDATE t1 0 X.. {i 1 {} {} t I} {{} {} {} {} t o}} 336} 337do_iterator_test 6.1.4 * { 338 SELECT indirect(0); 339 UPDATE t1 SET c = 'x' WHERE a = 1; 340 SELECT indirect(1); 341 UPDATE t1 SET c = 'i' WHERE a = 1; 342} { 343 {UPDATE t1 0 X.. {i 1 {} {} t o} {{} {} {} {} t i}} 344} 345do_iterator_test 6.1.4 * { 346 SELECT indirect(1); 347 UPDATE t1 SET c = 'y' WHERE a = 1; 348 SELECT indirect(1); 349 UPDATE t1 SET c = 'I' WHERE a = 1; 350} { 351 {UPDATE t1 1 X.. {i 1 {} {} t i} {{} {} {} {} t I}} 352} 353 354do_iterator_test 6.1.5 * { 355 INSERT INTO t2 VALUES(1, 'x'); 356} { 357 {INSERT t2 0 X. {} {i 1 t x}} 358 {INSERT t2 1 X. {} {i 2 n {}}} 359} 360 361do_iterator_test 6.1.6 * { 362 SELECT indirect(1); 363 INSERT INTO t2 VALUES(3, 'x'); 364 SELECT indirect(0); 365 UPDATE t2 SET y = 'y' WHERE x>2; 366} { 367 {INSERT t2 0 X. {} {i 3 t y}} 368 {INSERT t2 0 X. {} {i 4 t y}} 369} 370 371do_iterator_test 6.1.7 * { 372 SELECT indirect(1); 373 DELETE FROM t2 WHERE x = 4; 374 SELECT indirect(0); 375 INSERT INTO t2 VALUES(4, 'new'); 376} { 377 {UPDATE t2 0 X. {i 4 t y} {{} {} t new}} 378} 379 380sqlite3session S db main 381do_execsql_test 6.2.1 { 382 SELECT indirect(0); 383 SELECT indirect(-1); 384 SELECT indirect(45); 385 SELECT indirect(-100); 386} {0 0 1 1} 387S delete 388 389#------------------------------------------------------------------------- 390# Test that if a conflict-handler that has been passed either NOTFOUND or 391# CONSTRAINT returns REPLACE - the sqlite3changeset_apply() call returns 392# MISUSE and rolls back any changes made so far. 393# 394# 7.1.*: NOTFOUND conflict-callback. 395# 7.2.*: CONSTRAINT conflict-callback. 396# 397proc xConflict {args} {return REPLACE} 398test_reset 399 400do_execsql_test 7.1.1 { 401 CREATE TABLE t1(a PRIMARY KEY, b); 402 INSERT INTO t1 VALUES(1, 'one'); 403 INSERT INTO t1 VALUES(2, 'two'); 404} 405do_test 7.1.2 { 406 execsql { 407 CREATE TABLE t1(a PRIMARY KEY, b NOT NULL); 408 INSERT INTO t1 VALUES(1, 'one'); 409 } db2 410} {} 411do_test 7.1.3 { 412 set changeset [changeset_from_sql { 413 UPDATE t1 SET b = 'five' WHERE a = 1; 414 UPDATE t1 SET b = 'six' WHERE a = 2; 415 }] 416 set x [list] 417 sqlite3session_foreach c $changeset { lappend x $c } 418 set x 419} [list \ 420 {UPDATE t1 0 X. {i 1 t one} {{} {} t five}} \ 421 {UPDATE t1 0 X. {i 2 t two} {{} {} t six}} \ 422] 423do_test 7.1.4 { 424 list [catch {sqlite3changeset_apply db2 $changeset xConflict} msg] $msg 425} {1 SQLITE_MISUSE} 426do_test 7.1.5 { execsql { SELECT * FROM t1 } db2 } {1 one} 427 428do_test 7.2.1 { 429 set changeset [changeset_from_sql { UPDATE t1 SET b = NULL WHERE a = 1 }] 430 431 set x [list] 432 sqlite3session_foreach c $changeset { lappend x $c } 433 set x 434} [list \ 435 {UPDATE t1 0 X. {i 1 t five} {{} {} n {}}} \ 436] 437do_test 7.2.2 { 438 list [catch {sqlite3changeset_apply db2 $changeset xConflict} msg] $msg 439} {1 SQLITE_MISUSE} 440do_test 7.2.3 { execsql { SELECT * FROM t1 } db2 } {1 one} 441 442#------------------------------------------------------------------------- 443# Test that if a conflict-handler returns ABORT, application of the 444# changeset is rolled back and the sqlite3changeset_apply() method returns 445# SQLITE_ABORT. 446# 447# Also test that the same thing happens if a conflict handler returns an 448# unrecognized integer value. Except, in this case SQLITE_MISUSE is returned 449# instead of SQLITE_ABORT. 450# 451foreach {tn conflict_return apply_return} { 452 1 ABORT SQLITE_ABORT 453 2 567 SQLITE_MISUSE 454} { 455 test_reset 456 proc xConflict {args} [list return $conflict_return] 457 458 do_test 8.$tn.0 { 459 do_common_sql { 460 CREATE TABLE t1(x, y, PRIMARY KEY(x, y)); 461 INSERT INTO t1 VALUES('x', 'y'); 462 } 463 execsql { INSERT INTO t1 VALUES('w', 'w') } 464 465 set changeset [changeset_from_sql { DELETE FROM t1 WHERE 1 }] 466 467 set x [list] 468 sqlite3session_foreach c $changeset { lappend x $c } 469 set x 470 } [list \ 471 {DELETE t1 0 XX {t w t w} {}} \ 472 {DELETE t1 0 XX {t x t y} {}} \ 473 ] 474 475 do_test 8.$tn.1 { 476 list [catch {sqlite3changeset_apply db2 $changeset xConflict} msg] $msg 477 } [list 1 $apply_return] 478 479 do_test 8.$tn.2 { 480 execsql {SELECT * FROM t1} db2 481 } {x y} 482} 483 484 485#------------------------------------------------------------------------- 486# Try to cause an infinite loop as follows: 487# 488# 1. Have a changeset insert a row that causes a CONFLICT callback, 489# 2. Have the conflict handler return REPLACE, 490# 3. After the session module deletes the conflicting row, have a trigger 491# re-insert it. 492# 4. Goto step 1... 493# 494# This doesn't work, as the second invocation of the conflict handler is a 495# CONSTRAINT, not a CONFLICT. There is at most one CONFLICT callback for 496# each change in the changeset. 497# 498test_reset 499proc xConflict {type args} { 500 if {$type == "CONFLICT"} { return REPLACE } 501 return OMIT 502} 503do_test 9.1 { 504 execsql { 505 CREATE TABLE t1(a PRIMARY KEY, b); 506 } 507 execsql { 508 CREATE TABLE t1(a PRIMARY KEY, b); 509 INSERT INTO t1 VALUES('x', 2); 510 CREATE TRIGGER tr1 AFTER DELETE ON t1 BEGIN 511 INSERT INTO t1 VALUES(old.a, old.b); 512 END; 513 } db2 514} {} 515do_test 9.2 { 516 set changeset [changeset_from_sql { INSERT INTO t1 VALUES('x', 1) }] 517 sqlite3changeset_apply db2 $changeset xConflict 518} {} 519do_test 9.3 { 520 execsql { SELECT * FROM t1 } db2 521} {x 2} 522 523 524 525finish_test 526