"Igor Tandetnik" <[EMAIL PROTECTED]> wrote: > > Another way is to use sqlite3_interrupt. Before SQLite 3.3.7 (which I > believe is the latest version at this time)
3.3.8 was released yesterday (Monday) morning. I have not sent out an official announcement on this mailing list. Sorry. > sqlite3_interrupt could > only be called from the same thread that created the connection, which > as far as I can tell renders the function completely useless. sqlite3_interrupt() has long been used by the sqlite3 shell program. When you press control-C a posix signal handler invokes sqlite3_interrupt() to stop the current query. (This only works on posix, of course.) The original purpose of sqlite3_interrupt() was to support ^C in the shell, and for that purpose the thread restriction was entirely reasonable. It is easy to understand how this use of sqlite3_interrupt() might have escaped the notice of users on non-posix systems. -- D. Richard Hipp <[EMAIL PROTECTED]> ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
