In this case I have a text box where the user types in search results. I want to cancel all pending searches the moment they start typing something else.
On Mon, Apr 7, 2014 at 12:04 PM, E. Timothy Uy <t...@loqu8.com> wrote: > Isn't the interrupt in play until all active statements have been stopped? > Including statements that are added after the interrupt is called? I just > want to make sure it is safe to call the next statement. > > " Any new SQL statements that are started after the sqlite3_interrupt() > call and before the running statements reaches zero are interrupted as if > they had been running prior to the sqlite3_interrupt() call." > > > On Mon, Apr 7, 2014 at 11:52 AM, Richard Hipp <d...@sqlite.org> wrote: > >> On Mon, Apr 7, 2014 at 2:47 PM, E. Timothy Uy <t...@loqu8.com> wrote: >> >> > Hi, I am considering using sqlite3_interrupt to interrupt a long query - >> > but the documentation states that the order will stand until the >> activate >> > statement count is zero. How do I know that the activate statement >> count is >> > zero? >> > >> >> You could use http://www.sqlite.org/c3ref/stmt_busy.html >> >> Why do you think you need to know that? What does your application do >> differently if the active statement count is zero versus if it is not? >> >> >> >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> _______________________________________________ >> 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
