sqlite3_enable_shared_cache()

 ... In prior versions of SQLite, sharing was enabled or disabled for each thread separately. The cache sharing mode set by this interface effects all subsequent calls to sqlite3_open(), sqlite3_open_v2(), and sqlite3_open16(). Existing database connections continue to use the sharing mode ... 

struct sqlite3_value

 ... If SQLite is compiled to be single-threaded (with SQLITE_THREADSAFE=0 and with sqlite3_threadsafe() returning 0) or if SQLite is run in one of reduced mutex modes SQLITE_CONFIG_SINGLETHREAD or SQLITE_CONFIG_MULTITHREAD then there is no distinction between protected and unprotected sqlite3_value ... 

sqlite3_column_database_name(), sqlite3_column_database_name16(), sqlite3_column_table_name(), sqlite3_column_table_name16(), sqlite3_column_origin_name(), sqlite3_column_origin_name16()

 ... If two or more threads call one or more column metadata interfaces for the same prepared statement and result column at the same time then the results are undefined. See also lists of Objects, Constants, and Functions.

6. Options To Control Operating Characteristics  ... To put it another way, SQLITE_THREADSAFE=1 sets the default threading mode to Serialized. SQLITE_THREADSAFE=2 sets the default threading mode to Multi-threaded. And SQLITE_THREADSAFE=0 sets the threading mode to Single-threaded. The value of SQLITE_THREADSAFE can be ... 

 ... SQLITE_BUSY This return code indicates that another program or thread has the database locked. SQLite allows two or more threads to read the database at the same time, but only one thread can have the database open for writing at ... 

sqlite3_changes(), sqlite3_changes64()

 ... If a separate thread makes changes on the same database connection while sqlite3_changes() is running then the value returned is unpredictable and not meaningful. See also: the sqlite3_total_changes() interface the count_changes pragma the changes() SQL function the data_version pragma See ... 

sqlite3_busy_handler()

The sqlite3_busy_handler(D,X,P) routine sets a callback function X that might be invoked with argument P whenever an attempt is made to access a database table associated with database connection D when another thread or process has the ... 

sqlite3_last_insert_rowid()

 ... If a separate thread performs a new INSERT on the same database connection while the sqlite3_last_insert_rowid() function is running and thus changes the last insert rowid, then the value returned by sqlite3_last_insert_rowid() is unpredictable and might not equal either the ... 

 ... Read transactions versus write transactions SQLite supports multiple simultaneous read transactions coming from separate database connections, possibly in separate threads or processes, but only one simultaneous write transaction. A read transaction is used for reading only. A write transaction allows ... 

sqlite3_get_auxdata(), sqlite3_set_auxdata()

 ... These routines must be called from the same thread in which the SQL function is running. See also: sqlite3_get_clientdata() and sqlite3_set_clientdata(). See also lists of Objects, Constants, and Functions.