sqlite3_shutdown
Undo the effects of sqlite3_initialize(). Must not be called while there are outstanding database connections or memory allocations or while any part of SQLite is otherwise in use in any thread. This routine is not threadsafe. But it is safe to invoke this routine on when SQLite is already shut down. If SQLite is already shut down when this routine is invoked, then this routine is a harmless no-op.
Undo the effects of sqlite3_initialize(). Must not be called while there are outstanding database connections or memory allocations or while any part of SQLite is otherwise in use in any thread. This routine is not threadsafe. But it is safe to invoke this routine on when SQLite is already shut down. If SQLite is already shut down when this routine is invoked, then this routine is a harmless no-op.
Undo the effects of sqlite3_initialize(). Must not be called while there are outstanding database connections or memory allocations or while any part of SQLite is otherwise in use in any thread. This routine is not threadsafe. But it is safe to invoke this routine on when SQLite is already shut down. If SQLite is already shut down when this routine is invoked, then this routine is a harmless no-op.
Undo the effects of sqlite3_initialize(). Must not be called while there are outstanding database connections or memory allocations or while any part of SQLite is otherwise in use in any thread. This routine is not threadsafe. But it is safe to invoke this routine on when SQLite is already shut down. If SQLite is already shut down when this routine is invoked, then this routine is a harmless no-op.
Undo the effects of sqlite3_initialize(). Must not be called while there are outstanding database connections or memory allocations or while any part of SQLite is otherwise in use in any thread. This routine is not threadsafe. But it is safe to invoke this routine on when SQLite is already shut down. If SQLite is already shut down when this routine is invoked, then this routine is a harmless no-op.