Forum > Database

sqlite unexpected access violations

<< < (7/7)

Чебурашка:
For the whom this matters:

The answer to the issue opened in gitlab is "not a bug". It is normal that db components are not thread safe and the previously mentioned workaround (initialize/finalize-sqlite) is the solution to be used.

Thank you all for the support and the fpc levels for the answer.

I still don't understand why sqlite3dyn uses interlockedincrement to manipulate the refcount value, if the db components are not supposed to be thread-safe but it is not a problem, I am fine with the indication of using initialize/finalize.

TRon:
Thank you for the updates Чебурашка

Чебурашка:
Why the initialization process of the postgresql wrapper is made using critical sections, while the one of sqlite not?
At the end when are talking in both cases of loading a dll, connecting the exported methods, using a kind of refcount.

The two processes that have (basically) the same goal and the same way to achieve it, but they are made differently.

Is there a reason that I don't get? Thanks for any explanation.

Navigation

[0] Message Index

[*] Previous page