sqlite3_open(), sqlite3_open16()

 ... SQLITE_OPEN_NOMUTEX The new database connection will use the "multi-thread" threading mode. This means that separate threads are allowed to use SQLite at the same time, as long as each thread is using a different database connection. SQLITE_OPEN_FULLMUTEX The new ... 

2. Classic Serverless Vs. Neo-Serverless  ... The database engine runs within the same process, thread, and address space as the application. There is no message passing or network activity. Neo-Serverless: The database engine runs in a separate namespace from the application, probably on a separate ... 

sqlite3_sleep()

The sqlite3_sleep() function causes the current thread to suspend execution for at least a number of milliseconds specified in its parameter. If the operating system does not support sleep requests with millisecond time resolution, then the time will be rounded ... 

sqlite3_backup_init(), sqlite3_backup_step(), sqlite3_backup_finish(), sqlite3_backup_remaining(), sqlite3_backup_pagecount()

 ... Multiple threads may safely make multiple concurrent calls to sqlite3_backup_step(). However, the sqlite3_backup_remaining() and sqlite3_backup_pagecount() APIs are not strictly speaking threadsafe. If they are invoked at the same time as another thread is invoking sqlite3_backup_step() it is possible that they ... 

1.1. SQLite Is Different From Most Other SQL Databases  ... With MySQL, PostgreSQL, SQL-Server, and others, the application sends a message containing some SQL over to a separate server thread or process. That separate thread or process performs the requested I/O, then send the results back to the ... 

sqlite3_config()

 ... The application must ensure that no other SQLite interfaces are invoked by other threads while sqlite3_config() is running. The first argument to sqlite3_config() is an integer configuration option that determines what property of SQLite is to be configured. Subsequent arguments ... 

sqlite3_mutex_held(), sqlite3_mutex_notheld()

 ... These routines should return true if the mutex in their argument is held or not held, respectively, by the calling thread. The implementation is not required to provide versions of these routines that actually work. If the implementation does not ... 

sqlite3_total_changes(), sqlite3_total_changes64()

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

SQLITE_LIMIT_LENGTH, SQLITE_LIMIT_SQL_LENGTH, SQLITE_LIMIT_COLUMN, SQLITE_LIMIT_EXPR_DEPTH, SQLITE_LIMIT_COMPOUND_SELECT, SQLITE_LIMIT_VDBE_OP ... 

 ... SQLITE_LIMIT_WORKER_THREADS The maximum number of auxiliary worker threads that a single prepared statement may start. See also lists of Objects, Constants, and Functions.

sqlite3_aggregate_context()

 ... This routine must be called from the same thread in which the aggregate SQL function is running. See also lists of Objects, Constants, and Functions.