On Sat, Feb 20, 2010 at 4:28 AM, Max Vlasov <max.vla...@gmail.com> wrote:
> you mentioned full-text search.
> I just tried to search for mentioning of sqlite3_interrupt in the sqlite
> sources
> The main is the implemention of the function itself that just sets the
> isInterrupted variable:
>
> void sqlite3_interrupt(sqlite3 *db){
> db->u1.isInterrupted = 1;
> }
>
> but all of of fts_* sources lacks using this variable at all. I heard that
> fts is implemented a little separately to the main core code. So I suppose
> any job involving working with internal fts structures (packed data inside
> blobs) currently can ignore checking this variable. Can someone more
> familiar with the fts correct or confirm this?
The fts implementation does work in response to data gotten from
SQLite calls, and feeds data back out via SQLite calls, which should
all start throwing errors and causing things to unwind. Most
expensive fts operations involve lots of subsidiary queries into the
SQLite core, so I wouldn't expect it to take as long as is being
described for things to come back.
-scott
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
