To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How does sqlite return the status of the data base
Rick Pritchett <[EMAIL PROTECTED]> wrote:
> So how does it handle the transactions? Is it just however it
> retrieves them
What do you mean, "retrieves them"? Retrieves from w
It uses OS-level file locking.
Read http://sqlite.org/atomiccommit.html
g
-Original Message-
From: Igor Tandetnik [mailto:[EMAIL PROTECTED]
Sent: Friday, November 07, 2008 2:14 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How does sqlite return the status of the data base
Rick Pritchett <[EMAIL PROTECTED]> wrote:
> So how does it handle the transactions? Is it just however it
> retrieves them
What do you mean, "retrieves them"? Retrieves from where?
> or just which notices that the DB is available? And
> how does sql return the state its in to the proc?
When
TECTED]>
> Subject: Re: [sqlite] How does sqlite return the status of the data
> base?
> To: "General Discussion of SQLite Database" <sqlite-users@sqlite.org>
> Message-ID:
> <[EMAIL PROTECTED]>
>
> Content-Type: text/pl
Igor Tandetnik wrote:
> I'm not sure I understand the question. What precisely do you mean by
> "serialized queue"?
>
> Igor Tandetnik
>
Is it a repeated tautology?
>
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
>
ubject: Re: [sqlite] How does sqlite return the status of the data
base?
Rick Pritchett <[EMAIL PROTECTED]> wrote:
> Also does sqlite use a serialized queue for
> processing the
> transactions?
I'm not sure I understand the question. What precisely do you mean by
"seri
Rick Pritchett <[EMAIL PROTECTED]> wrote:
> What I would like to do is if the data base returns a busy or locked
> status is to set up my proc to retry the write. Or can I take care
> of this easier by setting a long timeout? And from what I read
> timeout basically keeps retrying the write for
from what I understood is that installing a busyhandler is equivalent to
use a loop around your sqlite3_step() that tests against busy state.
setting a timeout via sqlite3_busy_timeout works similar but doesn't
allow to trace the busy states.
please note that a LOCK state will not invoke the
What I would like to do is if the data base returns a busy or locked status is
to set up my proc to retry the write. Or can I take care of this easier by
setting a long timeout? And from what I read timeout basically keeps retrying
the write for a specified amount of time. Is this correct? Or
9 matches
Mail list logo