sqldb and threads

[Max V. Terentiev]

Hi,

I need to read/write SQLite database from several threads.

Should I create TSQLite3Connection in each thread ?

Or I can use single connection in many threads ? Should I use CriticalSections in this case ?

Thanks for help !

[Blestan]

not all functions of sqlite are thread safe .... create several connections in a pool and use them in the threads... do not use critical sections on one connection because if the app is heavely db active you will loose the advantages of multithreading ...
one possible solutions is to serialize the access to sqlite in one thread and use a event mechanisme to signal the threads that the db operations are executed ...

[Max V. Terentiev]

Sqlite have different compile-time threading options, including serialized where one connection can be shared betweern threads and multithreaded where each thread must have own connection.

But what about sqldb ? Is it threadsafe ?

[Blestan]

no idea about sdldb... why not use raw sqlite.dll? you can take a look at rqlite witch is a distribited sqlite and acess i rest based

[Leledumbo]

But what about sqldb ? Is it threadsafe ?

AFAIK it just relies on the underlying DBMS.

[taazz]

But what about sqldb ? Is it threadsafe ?

AFAIK it just relies on the underlying DBMS.

That is not enough. For example lcl relies on the underline widgetset as well but it is not thread safe, even when the underline widgetset is.

[Max V. Terentiev]

But in the end. Should I create should I create TSQLite3Connection in each thread ? Or I can use (in threads) single connection from main DataModule ?

[mangakissa]

You have to create TSQLite3Connection in each thread.
But be carefull. As I mentioned earlier, I don't know is the database will be locked for another transaction is the database is opened.

[Max V. Terentiev]

Thanks for help !