Home
last modified time | relevance | path

Searched refs:ROLLBACK (Results 1 – 25 of 112) sorted by relevance

12345

/external/chromium_org/third_party/sqlite/src/test/
Dsavepoint.test21 # and ROLLBACK TO comands are correctly parsed, and that the auto-commit
34 ROLLBACK TO sp1;
66 ROLLBACK TO sp1;
79 ROLLBACK TO SAVEPOINT sp3;
80 ROLLBACK TRANSACTION TO sp2;
81 ROLLBACK TRANSACTION TO SAVEPOINT sp1;
92 ROLLBACK TO sp1;
117 ROLLBACK TO one;
129 ROLLBACK TO one;
145 ROLLBACK TO two;
[all …]
Dtrigger9.test64 do_test trigger9-1.2.4 { execsql { ROLLBACK } } {}
79 do_test trigger9-1.3.3 { execsql { ROLLBACK } } {}
94 do_test trigger9-1.4.3 { execsql { ROLLBACK } } {}
109 do_test trigger9-1.5.3 { execsql { ROLLBACK } } {}
124 do_test trigger9-1.6.3 { execsql { ROLLBACK } } {}
139 do_test trigger9-1.7.3 { execsql { ROLLBACK } } {}
158 ROLLBACK;
175 ROLLBACK;
189 ROLLBACK;
204 ROLLBACK;
[all …]
Dtrigger3.test26 # Test that we can cause ROLLBACK, FAIL and ABORT correctly
37 WHEN (new.a = 3) THEN RAISE(ROLLBACK, 'Trigger rollback') END;
51 ROLLBACK;
69 ROLLBACK;
72 # ROLLBACK
86 # Verify that a ROLLBACK trigger works like a FAIL trigger if
110 ROLLBACK;
164 SELECT CASE WHEN (new.a = 1) THEN RAISE(ROLLBACK, 'View rollback')
Dtrans.test75 set v [catch {execsql {ROLLBACK TRANSACTION 'foo'}} msg]
178 ROLLBACK;
267 execsql {ROLLBACK}
326 ROLLBACK;
343 ROLLBACK;
398 ROLLBACK;
413 # within a transaction. Make sure ROLLBACK works.
421 ROLLBACK;
453 ROLLBACK;
483 ROLLBACK;
[all …]
Davtrans.test77 set v [catch {execsql {ROLLBACK TRANSACTION 'foo'}} msg]
179 ROLLBACK;
266 execsql {ROLLBACK}
325 ROLLBACK;
342 ROLLBACK;
397 ROLLBACK;
412 # within a transaction. Make sure ROLLBACK works.
420 ROLLBACK;
452 ROLLBACK;
482 ROLLBACK;
[all …]
DcorruptC.test159 catchsql {BEGIN; UPDATE t2 SET y='abcdef-uvwxyz'; ROLLBACK;}
179 catchsql {BEGIN; UPDATE t2 SET y='abcdef-uvwxyz'; ROLLBACK;}
191 catchsql {BEGIN; UPDATE t2 SET y='abcdef-uvwxyz'; ROLLBACK;}
207 catchsql {BEGIN; DELETE FROM t1 WHERE x>13; ROLLBACK;}
219 catchsql {BEGIN; DELETE FROM t1 WHERE x>13; ROLLBACK;}
231 catchsql {BEGIN; UPDATE t2 SET y='abcdef-uvwxyz'; ROLLBACK;}
243 catchsql {BEGIN; CREATE TABLE t3 AS SELECT x,3 as y FROM t2 WHERE rowid%5!=0; ROLLBACK;}
267 catchsql {BEGIN; CREATE TABLE t3 AS SELECT x,3 as y FROM t2 WHERE rowid%5!=0; ROLLBACK;}
358 catchsql {BEGIN; UPDATE t1 SET y=1; ROLLBACK;}
362 catchsql {BEGIN; UPDATE t2 SET y='abcdef-uvwxyz'; ROLLBACK;}
[all …]
Dsavepoint3.test27 ROLLBACK TO two;
57 ROLLBACK TO two;
58 ROLLBACK TO one;
104 # ROLLBACK TO abc;
132 ROLLBACK TO abc;
Dmemdb.test54 # This is used to test ROLLBACK. We gather a signature for t3, then
89 ROLLBACK;
102 ROLLBACK;
139 ROLLBACK;
170 7 {} {INSERT OR ROLLBACK} 1 {} {}
225 6 ROLLBACK {} UPDATE 1 {1 2 3 4} 0
230 11 ROLLBACK {} {UPDATE OR IGNORE} 0 {6 7 3 9} 1
235 16 {} {} {UPDATE OR ROLLBACK} 1 {1 2 3 4} 0
278 ROLLBACK;
320 ROLLBACK;
Djrnlmode3.test45 ROLLBACK;
67 ROLLBACK;
119 ROLLBACK;
141 db eval ROLLBACK
Dconflict.test52 7 {INSERT OR ROLLBACK} 1 {} {} 0
99 7 {INSERT OR ROLLBACK} 1 {} {}
144 7 {INSERT OR ROLLBACK} 1 {} {}
185 6 ROLLBACK INSERT 1 {} {}
190 11 ROLLBACK {INSERT OR IGNORE } 0 3 1
233 6 ROLLBACK INSERT 1 {} {}
238 11 ROLLBACK {INSERT OR IGNORE} 0 {} 1
243 16 {} {INSERT OR ROLLBACK} 1 {} {}
297 6 ROLLBACK UPDATE 1 {1 2 3 4} 0 0 0
302 11 ROLLBACK {UPDATE OR IGNORE} 0 {6 7 3 9} 1 0 0
[all …]
Dtkt2285.test31 ROLLBACK;
46 ROLLBACK;
Dsavepoint5.test13 # ROLLBACK TO that savepoint starts over again with another new
32 ROLLBACK TO sp1;
Dpager2.test98 execsql "ROLLBACK TO sp_$x"
122 # pager2-2.1: Test a ROLLBACK with journal_mode=off.
133 ROLLBACK;
Dtkt-d11f09d36e.test43 ROLLBACK;
53 ROLLBACK TO tr;
Dsavepoint4.test66 ROLLBACK TO two;
69 ROLLBACK TO one;
119 ROLLBACK TO one;
133 ROLLBACK TO three;
Dsavepoint2.test94 execsql "ROLLBACK to one"
113 execsql "ROLLBACK to two"
126 execsql "ROLLBACK to one"
132 # "ROLLBACK TO one" command above). So make a few changes to the
Dlock.test72 execsql {ROLLBACK}
168 execsql {ROLLBACK} db2
202 catch {execsql {ROLLBACK} db2}
228 catch {execsql {ROLLBACK} db2}
240 execsql {ROLLBACK}
261 execsql {ROLLBACK}
272 catch {db eval ROLLBACK}
292 execsql {ROLLBACK}
Dwhere9.test500 ROLLBACK;
518 ROLLBACK;
538 ROLLBACK
556 ROLLBACK;
573 ROLLBACK;
590 ROLLBACK;
607 ROLLBACK;
624 ROLLBACK;
640 ROLLBACK;
654 ROLLBACK;
[all …]
De_insert.test53 3 "INSERT OR ROLLBACK INTO main.a1 DEFAULT VALUES" {}
54 4 "INSERT OR ROLLBACK INTO a1 DEFAULT VALUES" {}
67 17 "INSERT OR ROLLBACK INTO main.a1 VALUES(1, 2)" {}
68 18 "INSERT OR ROLLBACK INTO a1 VALUES(1, 2)" {}
81 31 "INSERT OR ROLLBACK INTO main.a1 (b, a) VALUES(1, 2)" {}
82 32 "INSERT OR ROLLBACK INTO a1 (b, a) VALUES(1, 2)" {}
95 45 "INSERT OR ROLLBACK INTO main.a1 SELECT c, b FROM a2" {}
96 46 "INSERT OR ROLLBACK INTO a1 SELECT c, b FROM a2" {}
109 59 "INSERT OR ROLLBACK INTO main.a1 (b, a) SELECT c, b FROM a2" {}
110 60 "INSERT OR ROLLBACK INTO a1 (b, a) SELECT c, b FROM a2" {}
[all …]
Dtrans3.test13 # focus of this script is the response of COMMIT and ROLLBACK when
60 if {[catch {db eval ROLLBACK} errmsg]} {
DmallocC.test62 # written this was not the case. So do a manual ROLLBACK here so that the
67 ROLLBACK;
119 ROLLBACK;
Dtkt2409.test115 catchsql { ROLLBACK }
137 ROLLBACK;
183 catchsql { ROLLBACK }
222 catchsql { ROLLBACK }
Dioerr2.test52 # connection. Otherwise, try a ROLLBACK, in case a transaction
63 catch {execsql ROLLBACK}
87 ROLLBACK;
/external/chromium_org/sync/internal_api/public/
Dsync_manager_factory.h23 ROLLBACK, // Rollback sync manager enumerator
/external/chromium_org/sync/internal_api/
Dsync_manager_factory.cc27 case ROLLBACK: in CreateSyncManager()

12345