Add a note to the documentation of sqlite3_wal_hook() to say not to return SQLITE_ROW or SQLITE_DONE. Or any other value that is not a valid SQLite error code.
FossilOrigin-Name: 2f0b6cbf7b4fa31242ff4f6163226c22ae4f8c9b
This commit is contained in:
+4
-1
@@ -5784,7 +5784,10 @@ void sqlite3_log(int iErrCode, const char *zFormat, ...);
|
||||
** The callback function should normally return SQLITE_OK. ^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.
|
||||
** 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. ^Calling [sqlite3_wal_hook()] replaces any
|
||||
|
||||
Reference in New Issue
Block a user