On 10/06/2009 4:40 AM, Jeremy Smith wrote: > When I run sqlite3_interrupt, it doesn't close existing file handles, > making further searches tricky.
Which handles? How do you know? What does "tricky" mean -- "difficult but I can cope with it" or "causes an error" (if so, which?) or something else? > So I wrote code which clears all normal > file handles (fopen in shell.c), but... Have you tried calling sqlite3_finalize() on each prepared statement and sqlite3_close() on each open connection? > How do I close the database file too? It's not opened using fopen, but > with CreateFileA (in winOpen in os_win.c) so I don't know what to call > after calling sqlite3_interrupt. CloseHandle(global_h) just throws up an > error. And I can't do further searches until the database file is free. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
