This is exactly what I need. Thanks very much! Mi Chen
-----Original Message----- From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Igor Tandetnik Sent: Tuesday, December 03, 2013 7:46 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] sqlite3_interrupt() for controlled interruption On 12/3/2013 9:26 PM, Chen, Mi wrote: > I want to use sqlite3_interrupt() to interrupt the statement that is > executing sqlite3_step() for the first time in the worker. It is mutex > protected so I already make sure that when sqlite3_interrupt() is called, my > worker thread is running sqlite3_step()... > > However, the current sqlite3_interrupt() behavior is to interrupt all the > statements, including the ones that I suspended and running half-ways in the > background. I could make a separate database connection for each query, but > the ability for them to share data (e.g., temp tables) were limited. See if sqlite3_progress_handler helps. A progress handler only cancels one sqlite3_step() call. -- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
