Is there a good practice /setting for such high rate of concurrent writes
with reads ?
I understand that multiple readers with single writer at any time t is the
model which sqlite has with various locks/states (unlocked, pending ,
shared
, reserved , exclusive).
with is a bit unclear.
To
Hi,
Using sqlite version 3.6.x, so WAL mode not available. Need to see if i
need to upgrade to 3.7.x.
By the way, in WAL mode, i understand that whenever the WAL file reaches
1000 page of changes(which is the default), only then checkpoint/write
happens to the real database file .
On Sat, Nov 5, 2011 at 2:56 PM, swamir sw...@infineta.com wrote:
Hi,
Using sqlite version 3.6.x, so WAL mode not available. Need to see if i
need to upgrade to 3.7.x.
By the way, in WAL mode, i understand that whenever the WAL file reaches
1000 page of changes(which is the default),
Have a database and an application wherein , concurrent writes and reads
to/from the db happen (each DB connection is independent , autocommit mode
and no SQLITE_BUSY handler / timeout ).
I see Database is locked message.
Is there a good practice /setting for such high rate of concurrent writes
On 5 Nov 2011, at 3:32am, swamir wrote:
Will a busy_timeout setting for all connections and making write
transactions as begin immediate handle the situation ?
First, just try just setting a timeout and see if that fixes the problem.
http://www.sqlite.org/c3ref/busy_timeout.html
Simon.
