Jeremy Smith wrote: > John Machin wrote: >> On 10/06/2009 4:40 AM, Jeremy Smith wrote: >> >>> When I run sqlite3_interrupt, it doesn't close existing file >>> handles, making further searches tricky. >>> >> >> Which handles? How do you know? What does "tricky" mean -- "difficult >> but I can cope with it" or "causes an error" (if so, which?) or >> something else? >> > I mean that it's impossible to use the same data files or SQL database > file without running a new session (which means closing my GUI). So > not 'tricky', but 'impossible'.
There is a bug in your application. After a call to sqlite3_interrupt, you leave behind an open transaction. Naturally, any other connections are then blocked by that transaction. The only thing sqlite3_interrupt does is force a failure of sqlite3_step call currently in progress, if any. It doesn't finalize any statements, commit or roll back any transactions, or close any connections. It's your responsibility to do that, if that's your intent. Igor Tandetnik _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
