[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sqlite-users
Subject:    Re: [sqlite] Simple Sample Code [Linked]
From:       Simon Slavin <slavins () bigfraud ! org>
Date:       2010-05-31 14:50:19
Message-ID: C11DAD9F-D7CF-471C-956D-C59166CB2453 () bigfraud ! org
[Download RAW message or body]


On 31 May 2010, at 12:15pm, Black, Michael (IS) wrote:

> could I be so bold as to recommend you complete it with BUSY and LOCKED \
> possibilities?

Michael returns to a subject I would love someone to put some time into, but don't \
know enough to do myself.  I would like to see a fuller treatment of _BUSY and \
_LOCKED statuses with explanations and pseudocode and options.  Perhaps broken down \
by function, or perhaps just one for prepare->bind->step and one for the stand-alone \
functions which don't involve steps.

Most errors generated by SQLite are quite easy to handle: either they're fatal and \
your program should quit with an error message, or they're things you're \
intentionally testing so your program would obviously have code in to deal with them. \
But it's not obvious to me how to deal with _BUSY and _LOCKED.

Simon.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users


[prev in list] [next in list] [prev in thread] [next in thread]