SQLite is a desktop application, not a network aware application. The file
locking mechanisms lie to SQLite which makes it an EXTREMELY HIGH CHANCE
that connectivity and any WRITE statements WILL cause data corruption.
This isn't the fault of SQLite but the network file system locking. AFAIK,
Denis Y. Zibarev wrote:
>
> The problem goes down to winLock() implementation, particularly to
winLockFile() ...
>
I've made some experimental changes on the winLockHandle branch that should
address
this issue; however, I still need to add some tests to verify the new
behavior.
--
Joe
Hi there,
We use SQLite in our application to store the data, and some of our users
prefer to keep the files on a network drive. The application opens a connection
to sqlite database and keeps it open for a while, storing and retrieving the
data at user's request.
The issue that some clients
3 matches
Mail list logo