Small. Fast. Reliable.
Choose any three.

Search results 1..10 of 32 for: vacuum

VACUUM
(lang_vacuum.html)
 ... When in write-ahead log mode, only the auto_vacuum support property can be changed using VACUUM. By default, VACUUM operates on the main database. Attached databases can be vacuumed by appending the appropriate schema-name to the VACUUM statement. Compatibility ... 
The RBU Extension
(rbu.html)
3.1. RBU Vacuum Limitations When compared with SQLite's built-in VACUUM command, RBU Vacuum has the following limitations: It may not be used on a database that contains indexes on expressions. The database being vacuumed may not be in WAL mode.
 ... select-stmt signed-number simple-function-invocation simple-select-stmt sql-stmt sql-stmt-list table-constraint table-options table-or-subquery type-name update-stmt update-stmt-limited upsert-clause vacuum-stmt window-defn window-function-invocation with-clause
The Checksum VFS Shim
(cksumvfs.html)
4. Usage  ... sqlite3_exec(db, "VACUUM", 0, 0, 0); It never hurts to run the VACUUM, even if you don't need it. If the database is in WAL mode, you should shutdown and reopen all database connections before continuing. From the CLI ... 
 ... keywords math functions ON CONFLICT clause PRAGMA REINDEX RELEASE SAVEPOINT REPLACE RETURNING clause ROLLBACK TRANSACTION SAVEPOINT SELECT UPDATE UPSERT VACUUM window functions WITH clause The routines sqlite3_prepare_v2(), sqlite3_prepare(), sqlite3_prepare16(), sqlite3_prepare16_v2(), sqlite3_exec(), and sqlite3_get_table() accept an SQL statement list (sql-stmt ... 
Full-Featured SQL
(fullsql.html)
 ... advanced query planner Full-text search R-tree indexes JSON support The IS operator Table-valued functions REPLACE INTO VACUUM REINDEX The GLOB operator Hexadecimal integer literals The ON CONFLICT clause The INDEXED BY clause Virtual tables Multiple databases on ... 
PRAGMA auto_vacuum PRAGMA schema.auto_vacuum; PRAGMA schema.auto_vacuum = 0 | NONE | 1 | FULL | 2 | INCREMENTAL; Query or set the auto-vacuum status in the database. The default setting for auto-vacuum is 0 or "none", unless the SQLITE_DEFAULT_AUTOVACUUM compile-time option is used ... 
1. Overview  ... only the database schema and content. Hence the hash is constant even if the database file is modified by: VACUUM PRAGMA page_size PRAGMA journal_mode REINDEX ANALYZE copied via the backup API ... and so forth The operations above can potentially cause ... 
C API: SQL Keyword Checking
(c3ref/keyword_check.html)
sqlite3_keyword_count(), sqlite3_keyword_name(), sqlite3_keyword_check()
 ... For example, "VACUUM" is not a keyword if SQLite is compiled with the -DSQLITE_OMIT_VACUUM option. Also, new keywords may be added to future releases of SQLite. See also lists of Objects, Constants, and Functions.
C API: Autovacuum Compaction Amount Callback
(c3ref/autovacuum_pages.html)
sqlite3_autovacuum_pages()
 ... If no autovacuum pages callback is specified (the usual case) or a NULL pointer is provided for the callback, then the default behavior is to vacuum all free pages. So, in other words, the default behavior is the same as ... 

1234

Page generated by FTS5 in about 60.88 ms.