Review requested:

• @nodejs/sqlite

Concurrency Control

For concurrency control, SQLiteprovides a few options. Multi-threaded seems to be a good fit.

Multi-thread. In this mode, SQLite can be safely used by multiple threads provided that no singledatabase connection nor any object derived from database connection, such as aprepared statement, is used in two or more threads at the same time.

We just need a way to guarantee that no two threads will be usingconnection orstatements at the same time. Since we have a threadpool, hence no control over which thread a work will be executed, seems like we need a mutex. Please share your thoughts.

We just need a way to guarantee that no two threads will be usingconnection orstatements at the same time. Since we have a threadpool, hence no control over which thread a work will be executed, seems like we need a mutex. Please share your thoughts.

I wonder if, for the first version of this API if theserialized mode is good enough

Serialized. In serialized mode, API calls to affect or use any SQLitedatabase connection or any object derived from such a database connection can be made safely from multiple threads. The effect on an individual object is the same as if the API calls had all been made in the same order from a single thread. The name "serialized" arises from the fact that SQLite uses mutexes to serialize access to each object.