Small. Fast. Reliable.
Choose any three.

Search results 21..30 of 32 for: vacuum

C API: Online Backup API.
(c3ref/backup_finish.html)
sqlite3_backup_init(), sqlite3_backup_step(), sqlite3_backup_finish(), sqlite3_backup_remaining(), sqlite3_backup_pagecount()
 ... The VACUUM INTO command. The sqlite3_rsync utility program. See also lists of Objects, Constants, and Functions.
1.2. Example Output  ... Pages of auto-vacuum overhead The number of pages that store data used by the database to facilitate auto-vacuum. This is zero for databases that do not support auto-vacuum. Number of tables in the database The number of ... 
Database File Format
(fileformat.html)
1.3.12. Incremental vacuum settings The two 4-byte big-endian integers at offsets 52 and 64 are used to manage the auto_vacuum and incremental_vacuum modes. If the integer at offset 52 is zero then pointer-map (ptrmap) pages are omitted from the database file ... 
Syntax Diagrams For SQLite
(syntaxdiagrams.html)
 ... Used by:   insert-stmt References:   column-name-list   expr   indexed-column See also:   lang_createtrigger.html   lang_insert.html   lang_upsert.html vacuum-stmt: Used by:   sql ... 
SQLite Older News
(oldnews.html)
 ... And the kind of corruption that the bug causes can usually be fixed simply by running VACUUM. Nevertheless, because the bug can result in database corruption, it is recommended that all SQLite users upgrade to version 3.7.2 or ... 
Compile-time Options
(compile.html)
9. Options To Omit Features  ... Executing a PRAGMA auto_vacuum statement is not an error (since unknown PRAGMAs are silently ignored), but does not return a value or modify the auto-vacuum flag in the database file. If a database that supports auto-vacuum is opened ... 
8.2. Corruption following switches between rollback and WAL modes Repeatedly switching an SQLite database in and out of WAL mode and running the VACUUM command in between switches, in one process or thread, can cause another process or thread that has the database file open to miss the fact ... 
4. The Opcodes  ... Vacuum Vacuum the entire database P1. P1 is 0 for "main", and 2 or more for an attached database. The "temp" database may not be vacuumed. If P2 is not zero, then it is a register holding a string which ... 
C API: Standard File Control Opcodes
(c3ref/c_fcntl_begin_atomic_write.html)
SQLITE_FCNTL_LOCKSTATE, SQLITE_FCNTL_GET_LOCKPROXYFILE, SQLITE_FCNTL_SET_LOCKPROXYFILE, SQLITE_FCNTL_LAST_ERRNO, SQLITE_FCNTL_SIZE_HINT, SQLITE_FCNTL_CHUNK_SIZE ... 
 ... This is used by VACUUM operations. The SQLITE_FCNTL_VFSNAME opcode can be used to obtain the names of all VFSes in the VFS stack. The names are of all VFS shims and the final bottom-level VFS are written into memory ... 
Write-Ahead Logging
(wal.html)
1. Overview  ... It is not possible to change the page_size after entering WAL mode, either on an empty database or by using VACUUM or by restoring from a backup using the backup API. You must be in a rollback journal mode to ... 

1234

Page generated by FTS5 in about 59.12 ms.