Some ideas:
Sqlite may return that the database is locked immediately if it detects a
deadlock situation. Something like: a different connection holds a reserved
lock (waiting for read connections to close so it can promote to exclusive),
and the current connection tries to promote from a read
On 3 Jul 2018, at 8:08pm, Phani Rahul Sivalenka
wrote:
> As per our observation, the initial write operations on the sqlite db file
> throw "db is locked" error. After a certain time (around an hour) write
> operations start working and we are able to do all the operations as
> required. [...]
As per our observation, the initial write operations on the sqlite db file
throw "db is locked" error. After a certain time (around an hour) write
operations start working and we are able to do all the operations as
required.
On Mon, Jun 25, 2018 at 7:37 PM Phani Rahul Sivalenka
wrote:
> >
> SQLiteConnectionStringBuilder connBuilder = new
> SQLiteConnectionStringBuilder();
We are setting these configs via the connection string in xml. This is same as
the above. The following is the connection string that we are using:
“data
On 21 Jun 2018, at 10:01pm, Phani Rahul Sivalenka
wrote:
> When we do a read operation and write/update operation on the SQLite DB,
> the write operation gets timed out saying the “db is locked”.
[...]
> - Busy Timeout : 30sec
> - Default Timeout : 30sec
I'm going to assume you're doing
Hello,
We have an ASP.NET Web application running with Mono on Linux. Uses
System.Data.SQLite library with an interop generated with a specific set
configuration to interact with the SQLite file.
When we do a read operation and write/update operation on the SQLite DB,
the write operation gets
6 matches
Mail list logo
