Home
last modified time | relevance | path

Searched refs:VACUUM (Results 1 – 25 of 50) sorted by relevance

12

/external/chromium_org/third_party/sqlite/src/test/
Dvacuum.test12 # focus of this file is testing the VACUUM statement.
19 # If the VACUUM statement is disabled in the current build, skip all
59 # internally by VACUUM, to ensure that VACUUM falls back
72 VACUUM;
107 VACUUM;
121 VACUUM;
123 } {1 {cannot VACUUM from within a transaction}}
143 VACUUM
173 VACUUM;
205 # Ticket #427. Make sure VACUUM works when the EMPTY_RESULT_CALLBACKS
[all …]
De_vacuum.test70 do_execsql_test e_vacuum-0.1 { VACUUM } {}
77 # EVIDENCE-OF: R-60541-63059 Running VACUUM to rebuild the database
106 do_execsql_test e_vacuum-1.1.$tn.4 {VACUUM} {}
116 # EVIDENCE-OF: R-05791-54928 Running VACUUM ensures that each table and
121 # e_vacuum-1.2.3 - Run VACUUM.
138 do_execsql_test e_vacuum-1.2.3 { VACUUM } {}
171 execsql VACUUM
176 # auto_vacuum support property can be changed using VACUUM.
186 execsql VACUUM
191 # EVIDENCE-OF: R-38001-03952 VACUUM only works on the main database. It
[all …]
Dvacuum2.test12 # focus of this file is testing the VACUUM statement.
24 # If the VACUUM statement is disabled in the current build, skip all
43 VACUUM;
60 VACUUM
67 # autovacuum setting, do a VACUUM, and the new setting takes effect.
94 VACUUM;
116 VACUUM;
210 db eval {SELECT a, b FROM t1} { if {$a == 8} { execsql VACUUM } }
212 } {1 {cannot VACUUM - SQL statements in progress}}
216 db eval {SELECT 1, 2, 3} { execsql VACUUM }
[all …]
Dvacuum3.test13 # VACUUM statement.
20 # If the VACUUM statement is disabled in the current build, skip all
61 VACUUM;
83 VACUUM;
110 VACUUM;
185 VACUUM;
216 VACUUM;
226 VACUUM;
233 VACUUM;
246 VACUUM;
[all …]
Dpagerfault3.test41 VACUUM;
46 # Now do the page-size change and VACUUM with IO error injection. When
56 VACUUM;
Dtkt-5d863f876e.test29 VACUUM;
42 VACUUM;
Dtkt-d82e3f3721.test50 VACUUM;
74 VACUUM;
Dpagesize.test122 execsql {VACUUM}
183 ifcapable {vacuum} {execsql VACUUM}
188 ifcapable {vacuum} {execsql VACUUM}
Dfts3b.test41 db eval {VACUUM}
43 # The VACUUM renumbered the t1_content table in fts2, which breaks
96 db eval {VACUUM}
98 # The VACUUM renumbered the t2_segment table in fts2, which would
Drecover2.test73 db eval {VACUUM}
98 db eval {VACUUM}
123 db eval {VACUUM}
148 db eval {VACUUM}
DwhereA.test53 VACUUM;
67 VACUUM;
Dvacuum4.test20 # If the VACUUM statement is disabled in the current build, skip all
65 VACUUM;
Dfallocate.test103 execsql { VACUUM }
118 VACUUM;
Dwalbak.test67 # Try a VACUUM on a WAL database.
71 VACUUM;
91 execsql { VACUUM }
Dtkt1512.test48 VACUUM;
Dalter3.test47 # alter3-7.*: Test that VACUUM resets the file-format.
340 VACUUM;
365 VACUUM;
Dtkt3762.test41 VACUUM;
Dcrash7.test73 VACUUM;
Ddescidx1.test325 execsql {VACUUM}
350 execsql {VACUUM}
356 VACUUM;
Dtrace.test88 db eval VACUUM
90 } {VACUUM}
Dioerr.test48 # Test for IO errors during a VACUUM.
51 # the file-header of the temporary database used by VACUUM. Since the
75 VACUUM;
455 VACUUM;
Ddiskfull.test82 do_diskfull_test diskfull-2 VACUUM
Dspeed2.test128 speed_trial speed2-vacuum1 100000 row VACUUM
199 speed_trial speed2-vacuum2 100000 row VACUUM
/external/chromium_org/third_party/sqlite/src/ext/rtree/
Drtree7.test40 VACUUM;
53 VACUUM;
/external/chromium_org/third_party/sqlite/src/tool/
Dmkkeywordhash.c122 # define VACUUM 0 macro
124 # define VACUUM 0x00004000 macro
261 { "VACUUM", "TK_VACUUM", VACUUM },

12