[sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread)

We tried already, still fail without correct recovery. > From: slavins at bigfraud.org > Date: Tue, 11 Aug 2015 03:43:59 +0100 > To: sqlite-users at mailinglists.sqlite.org > Subject: Re: [sqlite] Fwd: Problem with SQLite in C++. DB is BUSY > (Multithread) > > > O

[sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread)

t;> c> locked. Is this because we don't create and handle savepoints >> c> correct? One way to avoid the continuous abort is we use begin >> c> transaction IMMEDIATE to wrap all our operations but it looks like >> c> our solution is bandage. I don'

[sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread)

will be the best solution to solve our issue. If anyone could help answer it, I appreciate. > Date: Mon, 10 Aug 2015 15:40:17 +0300 > From: dm3chip at gmail.com > To: sqlite-users at mailinglists.sqlite.org > Subject: [sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread) > > --

[sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread)

On 11 Aug 2015, at 2:28am, ch wrote: > Is this because we don't create and handle savepoints correct? Have you set a timeout value using the routine I pointed to earlier ? If not, do so. Simon.

[sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread)

0300 >> From: dm3chip at gmail.com >> To: sqlite-users at mailinglists.sqlite.org >> Subject: [sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread) >> >> -- Forwarded message -- >> From: ??? ??? >> Date: 2015-08-

[sqlite] Fwd: Problem with SQLite in C++. DB is BUSY (Multithread)

-- Forwarded message -- From: ??? ??? Date: 2015-08-10 0:37 GMT+03:00 Subject: Problem with SQLite in C++. DB is BUSY (Multithread) To: sqlite-users at mailinglists.sqlite.org Hello! I've got a problem. I'm using sqlite3 in my C++ project. In the