Home
last modified time | relevance | path

Searched refs:sqlite3_unlock_notify (Results 1 – 10 of 10) sorted by relevance

/sqlite-3.40.0/test/
H A Dnotify1.test12 # focus of this file is testing the sqlite3_unlock_notify() API.
60 # (which is the equivalent of invoking sqlite3_unlock_notify() with
400 sqlite3_unlock_notify db3
H A Dnotify2.test21 # it is just a demonstration of how the sqlite3_unlock_notify() function
247 puts "The following test seeks to demonstrate that the sqlite3_unlock_notify()"
H A Dnotify3.test12 # focus of this file is testing the sqlite3_unlock_notify() API.
/sqlite-3.40.0/src/
H A Dnotify.c148 int sqlite3_unlock_notify( in sqlite3_unlock_notify() function
H A Dloadext.c368 sqlite3_unlock_notify,
H A Dtest_thread.c455 rc = sqlite3_unlock_notify(db, unlock_notify_cb, (void *)&un); in wait_for_unlock_notify()
H A Dsqlite3ext.h569 #define sqlite3_unlock_notify sqlite3_api->unlock_notify macro
H A Dsqlite.h.in9083 ** sqlite3_unlock_notify() method with the blocked connection handle as
9089 ** ^(If sqlite3_unlock_notify() is called in a multi-threaded application,
9093 ** from within the call to sqlite3_unlock_notify().)^
9101 ** blocked connection. If sqlite3_unlock_notify() is called when the
9103 ** then the new callback replaces the old.)^ ^If sqlite3_unlock_notify() is
9113 ** ^Unless deadlock is detected (see below), sqlite3_unlock_notify() always
9144 ** To avoid this scenario, the sqlite3_unlock_notify() performs deadlock
9145 ** detection. ^If a given call to sqlite3_unlock_notify() would put the
9160 ** always appropriate to call sqlite3_unlock_notify(). There is however,
9165 ** sqlite3_unlock_notify() results in the unlock-notify callback being
[all …]
H A Dtclsqlite.c3514 if( sqlite3_unlock_notify(pDb->db, xNotify, pNotifyArg) ){ in DbObjCmd()
H A Dtest1.c6932 rc = sqlite3_unlock_notify(db, test_unlock_notify_cb, (void *)interp); in test_unlock_notify()