[sqlite] Site unavailable.

In Russia when I'm trying to visit sqlite.org site, I'm getting conection timeout. Also, sqlite.org doesn't pinged.

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

Thank you for answers, but I have already solved this problem. I set busy timeout for both connections. ???, 11 ??? 2015 ?. Simon Slavin ???: > > On 11 Aug 2015, at 2:28am, ch > > wrote: > > > Is this because we don't create and handle savepoints correct? > > Have you

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

Thank you for help and explain WAL mode. 2015-08-11 1:22 GMT+03:00 Simon Slavin : > > On 10 Aug 2015, at 11:12pm, ??? ??? wrote: > > > But what is minimum period? > > The minimum period doesn't matter. > > The number you set the timeout to is the /maximum/ period. SQLite will >

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

But what is minimum period? 2015-08-11 0:56 GMT+03:00 Simon Slavin : > > On 10 Aug 2015, at 10:49pm, ??? ??? wrote: > > > When I set timeout to 12 ms (2 minutes). It starts work. But as I > > understand from reading SQLite C interface, when DB in WAL journal mode > it > > should

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

When I set timeout to 12 ms (2 minutes). It starts work. But as I understand from reading SQLite C interface, when DB in WAL journal mode it should work without busytimeout. Can it work without busy timeout? 2015-08-10 17:11 GMT+03:00 Simon Slavin : > > On 9 Aug 2015, at 10:37pm, ???

[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

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

Hello! I've got a problem. I'm using sqlite3 in my C++ project. In the log I've got error's *DB is locked error code 5*. As I know error code 5 means, that DB is busy. To solve this I started to use WAL journal mode. But it doesn't help. In my program I've got 2 connections to the same db. I use