*** DRAFT ***
int sqlite3_db_cacheflush(sqlite3*);
R-30842-64597:[If a write-transaction is open on database connection D when the sqlite3_db_cacheflush(D) interface invoked, any dirty pages in the pager-cache that are not currently in use are written out to disk. ] A dirty page may be in use if a database cursor created by an active SQL statement is reading from it, or if it is page 1 of a database file (page 1 is always "in use"). R-39070-64522:[The sqlite3_db_cacheflush(D) interface flushes caches for all schemas - "main", "temp", and any attached databases. ]
R-03511-33422:[If this function needs to obtain extra database locks before dirty pages can be flushed to disk, it does so. ] R-29872-04040:[If those locks cannot be obtained immediately and there is a busy-handler callback configured, it is invoked in the usual manner. ] R-33800-32193:[If the required lock still cannot be obtained, then the database is skipped and an attempt made to flush any dirty pages belonging to the next (if any) database. ] R-54967-64139:[If any databases are skipped because locks cannot be obtained, but no other error occurs, this function returns SQLITE_BUSY. ]
R-14174-63475:[If any other error occurs while flushing dirty pages to disk (for example an IO error or out-of-memory condition), then processing is abandoned and an SQLite error code is returned to the caller immediately. ]
R-13164-16564:[Otherwise, if no error occurs, sqlite3_db_cacheflush() returns SQLITE_OK. ]
R-54592-23151:[This function does not set the database handle error code or message returned by the sqlite3_errcode() and sqlite3_errmsg() functions. ]
See also lists of Objects, Constants, and Functions.
*** DRAFT ***