Hi All,
This is the exaclty approach that I used in my code.
No way to reduce/minimize the lock issue regardless about the reading or the
writting.
We need to have to code to sleep and re-try the command again.
JP
----- Original Message ----
From: Richard Klein <[EMAIL PROTECTED]>
To: sqlite-users@sqlite.org
Sent: Wednesday, December 12, 2007 11:59:04 AM
Subject: Re: [sqlite] Occasional Database is Locked Error
Mark Riehl wrote:
> Am I just getting [un]lucky and issuing selects at the same time I'm
> writing from the other process?
Yes.
> I'm planning on using a web-based app
> to periodically poll the database (to provide summary information)
> while the C++ app performs the inserts. What is the best way to
> reduce/minimize the lock issue?
There is no way to reduce/minimize the lock issue. "Database is locked"
is a "normal" error return that your polling app must be prepared to deal
with. As other folks have noted, the way to deal with it is to sleep for
awhile and then retry the SELECT.
- Richard Klein
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
