"Roger Binns" <[EMAIL PROTECTED]> wrote: > Is it safe to have one sqlite3* in one thread doing various operations > and then calling sqlite3_interrupt from another thread on that same > sqlite3* pointer? Or does sqlite3_interrupt always have to be called > in the same thread as the operations? > > The doc doesn't say anything either way. The code is pretty trivial > only changing (sqlite3*)db->flags but that isn't done under any form > of mutex and looks like race conditions could cause problems. >
No, it is not safe to invoke sqlite3_interrupt from a different thread. Though now that you mention it, I can see where that might be useful. I might change it so that sqlite3_interrupt can be safely invoked from a different thread for the next release. -- D. Richard Hipp <[EMAIL PROTECTED]>
