-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Smith wrote: > When I run sqlite3_interrupt, it doesn't close existing file handles,
Why would it? sqlite3_interrupt sets a flag on the sqlite3 handle. Various operations periodically check the flag and if it is true then error out with SQLITE_INTERRUPT. It does not terminate or clean up anything. In your example you would have one thread calling sqlite3_step which is taking a long time and another thread calling sqlite3_interrupt. The first thread would notice and sqlite3_step would return SQLITE_INTERRUPT. At that point it is up to you what to do. You can prepare new queries to execute, call sqlite3_reset to run the query again, or finalize the statements and call sqlite3_close on the connection. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkouwS8ACgkQmOOfHg372QTu8wCfa2/XM75a0A4LAaWbiMaE+/xJ 1YEAoMJp2/A19GdABeRRgjswKn7gMTnr =i+lq -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
