Martin Alfredsson <[EMAIL PROTECTED]> wrote:
>
> I understand, I to did not understand what happened.
> But the code below shows my point (sorry for the horrible indentation).
Rather than apologize, why not just fix it? Is your time so
much more valuable than ours that you cannot be troubled wit
[snip]
> if (sqlite3_prepare(db, "SELECT * FROM tbookings", -1, &rs,
> &psz) ==
> SQLITE_OK)
> {
> rc = SQLITE_ROW;
> while (rc == SQLITE_ROW)
>{
>
>From: Igor Tandetnik <[EMAIL PROTECTED]>
>Subject: Re: Where to look in the code for this ?
>Newsgroups: gmane.comp.db.sqlite.general
>Date: 2006-10-02 21:53:13 GMT (1 hour and 1 minute ago)
>Martin Alfredsson <[EMAIL PROTECTED]> wrote:
>>> Surely you mean "until the process completes its write
>>Martin Alfredsson <[EMAIL PROTECTED]> wrote:
>> My problem is that the SHARED lock does not stay after
>>_step() returns
>> SQLITE_DONE and that this allows another process to update the
>> database and I end up with a locked database.
>Why exactly is this a bad thing? When sqlite3_step return
Anyone familiar with SQLite source ?
Opened a tecked a few days ago (#1995). However I did not check enough
and found out I only got the error in a subset of the tests;
My problem is that the SHARED lock does not stay after _step() returns
SQLITE_DONE and that this allows another process to upda
5 matches
Mail list logo