*** DRAFT ***
void *sqlite3_wal_hook( sqlite3*, int(*)(void *,sqlite3*,const char*,int), void* );
R-00752-43975:[The sqlite3_wal_hook() function is used to register a callback that is invoked each time data is committed to a database in wal mode. ]
R-65366-15139:[The callback is invoked by SQLite after the commit has taken place and the associated write-lock on the database released ] , so the implementation may read, write or checkpoint the database as required.
R-52629-38967:[The first parameter passed to the callback function when it is invoked is a copy of the third parameter passed to sqlite3_wal_hook() when registering the callback. ] R-23378-42536:[The second is a copy of the database handle. ] R-44294-52863:[The third parameter is the name of the database that was written to - either "main" or the name of an ATTACH-ed database. ] R-18913-19355:[The fourth parameter is the number of pages currently in the write-ahead log file, including those that were just committed. ]
The callback function should normally return SQLITE_OK. R-14034-00929:[If an error code is returned, that error will propagate back up through the SQLite code base to cause the statement that provoked the callback to report an error, though the commit will have still occurred. ] If the callback returns SQLITE_ROW or SQLITE_DONE, or if it returns a value that does not correspond to any valid SQLite error code, the results are undefined.
A single database handle may have at most a single write-ahead log callback registered at one time. R-10466-53920:[Calling sqlite3_wal_hook() replaces any previously registered write-ahead log callback. ] R-39756-42402:[The return value is a copy of the third parameter from the previous call, if any, or 0. ] R-57445-43425:[Note that the sqlite3_wal_autocheckpoint() interface and the wal_autocheckpoint pragma both invoke sqlite3_wal_hook() and will overwrite any prior sqlite3_wal_hook() settings. ]
See also lists of Objects, Constants, and Functions.
*** DRAFT ***