Searched refs:sqlite3_close_v2 (Results 1 – 9 of 9) sorted by relevance
34 sqlite3_close_v2 $DB40 sqlite3_close_v2 $DB50 sqlite3_close_v2 $DB65 sqlite3_close_v2 $DB85 sqlite3_close_v2 $DB
68 # 1. A wal mode db is opened and written. Then sqlite3_close_v2() used87 # a statement and call sqlite3_close_v2() (so that the statement handle101 sqlite3_close_v2 $::db1
172 if( pDb ) capi.sqlite3_close_v2(pDb);519 capi.sqlite3_close_v2(pDb);
384 sqlite3_close_v2,
577 #define sqlite3_close_v2 sqlite3_api->close_v2 macro
1292 int sqlite3_close_v2(sqlite3 *db){ return sqlite3Close(db,1); } in sqlite3_close_v2() function
266 ** and [sqlite3_close_v2()] are its destructors. There are many other319 ** ^The sqlite3_close() and sqlite3_close_v2() routines are destructors321 ** ^Calls to sqlite3_close() and sqlite3_close_v2() return [SQLITE_OK] if332 ** [SQLITE_BUSY]. ^If sqlite3_close_v2() is called with unfinalized prepared338 ** are closed, and all backups have finished. The sqlite3_close_v2() interface345 ** The C parameter to [sqlite3_close(C)] and [sqlite3_close_v2(C)]350 ** ^Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer354 int sqlite3_close_v2(sqlite3*);
718 rc = sqlite3_close_v2(db); in sqlite_test_close_v2()
503 if(pDb) capi.sqlite3_close_v2(pDb);