I tested the trial version of the latest UniDAC and noticed that the SQLite Direct Mode library for Linux is compiled with:

THREADSAFE=0
MUTEX_OMIT

sqlite3_threadsafe() also returns 0.

At the same time, the Windows SQLite libraries are compiled with THREADSAFE=1.

Is this difference intentional?

Will the Linux version work correctly in a multithreaded application if each thread uses its own separate TUniConnection / SQLite connection?

As far as I understand, SQLite documentation says that with SQLITE_THREADSAFE=0, SQLite must not be used concurrently from multiple threads, even when different connections are used.

Does UniDAC add some additional synchronization around SQLite calls on Linux, or is multithreaded use of SQLite Direct Mode not supported in this configuration?

I would like to understand whether this is expected behavior or a build configuration issue.