OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:vacuum
(Results
76 - 100
of
128
) sorted by null
1
2
3
4
5
6
/external/chromium_org/third_party/sqlite/src/test/
alter4.test
39
# alter4-7.*: Test that
VACUUM
resets the file-format.
backup_ioerr.test
32
# on whether or not auto-
vacuum
is configured. Test cases backup_ioerr-1.*
speed4.test
206
VACUUM
;
speed4p.explain
242
VACUUM
;
speed4p.test
254
VACUUM
;
backup.test
484
# backup-5.x.5.*: Database is shrunk via incr-
vacuum
.
568
execsql {
VACUUM
} $writer
587
VACUUM
;
pagerfault.test
90
VACUUM
;
940
# This tests fault-injection in a special case in the auto-
vacuum
code.
[
all
...]
dbstatus.test
196
# Additionally, in auto-
vacuum
mode, dropping tables and indexes causes
memdb.test
408
# Test that auto-
vacuum
works with in-memory databases.
nan.test
160
VACUUM
;
malloc.test
175
ifcapable
vacuum
{
193
VACUUM
;
savepoint.test
369
# The following tests, savepoint-6.*, test an incr-
vacuum
inside of a
761
# auto-
vacuum
mode.
/external/chromium_org/third_party/sqlite/src/tool/
mksqlite3c.tcl
284
vacuum
.c
showdb.c
173
print_decode_line(aData, 64, 4, "Incremental-
vacuum
mode");
/external/chromium_org/third_party/sqlite/src/
main.mk
67
update.o util.o
vacuum
.o \
157
$(TOP)/src/
vacuum
.c \
Makefile.vxworks
212
update.o util.o
vacuum
.o \
295
$(TOP)/src/
vacuum
.c \
manifest
237
F src/
vacuum
.c 05513dca036a1e7848fe18d5ed1265ac0b32365e
[
all
...]
/external/chromium_org/chrome/browser/extensions/activity_log/
fullstream_ui_policy.cc
369
"
VACUUM
"));
/external/chromium_org/third_party/sqlite/src/src/
btree.c
[
all
...]
parse.y
201
SAVEPOINT TEMP TRIGGER
VACUUM
VIEW VIRTUAL
[
all
...]
prepare.c
240
** meta[6] Incremental
vacuum
mode
304
** clear the legacy_file_format pragma flag so that a
VACUUM
will
/external/chromium_org/third_party/sqlite/src/ext/fts1/
fts1.c
12
** and expects the rowid to not change. The SQLite
VACUUM
operation
14
** fts1 in a system which has disabled
VACUUM
, then you can continue
16
**
VACUUM
, though systems using auto_vacuum are unlikely to invoke
17
**
VACUUM
.
19
** fts1 should be safe even across
VACUUM
if you only insert documents
[
all
...]
/external/chromium_org/chrome/browser/history/
thumbnail_database.cc
635
void ThumbnailDatabase::
Vacuum
() {
638
ignore_result(db_.Execute("
VACUUM
"));
[
all
...]
history_backend.cc
[
all
...]
/external/chromium_org/sql/
connection.h
231
// running "PRAGMA auto_vacuum = 1;" then "
VACUUM
".
Completed in 755 milliseconds
1
2
3
4
5
6