> Scott meant that most of the job fts is doing is actually calls to sqlite
> core that checks this state very often. I just did a windows desktop test
> with the fts3, my second thread is ordered to call sqlite_interrupt after 1
> second sleep and different tests confirms his explanation (including phrase
> search and mask search), everything works fine.
I'm not sure I should keep bombing the list with this (just tell me when you
can't stand me anymore ;-) ) but as I said initially, I'm developing on a first
gen iPod Touch and the same query that takes tens of seconds on this device is
quite fast on the simulator that Apple provides.
I also can stop the process between any two calls to sqlite3_step, my issue is
with the first one that (to me) does not seem interruptible.
I just tried adding a call to CHECK_FOR_INTERRUPT just after "for(pc=p->pc;
rc==SQLITE_OK; pc++){" (~line 52715 in the ammalgamation) in sqlite3VdbeExec.
It now behaves to my satisfaction (I can interrupt my query in no time)
So I guess my question now becomes: is it safe?
Simon.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
