Hi, seems like sqlite_interrupt() does not cancel ATTACHing of blocked database.
Steps to reproduce problem: 1. open 'foo.db' in shell, run 'BEGIN EXCLUSIVE'; 2. switch to custom application and open ":memory:" database in it; set busy timeout to 15 seconds and run "ATTACH 'foo.db' as db" in thread A; 3. wait 2-3 seconds and call sqlite_interrupt(<same_connection_to_db>) in thread B; 4. nothing happens: application still waits 15 seconds and receives SQLITE_BUSY error. SQLite should immediately stop waiting for database (upon sqlite_interrupt() call) and return with SQLITE_INTERRUPT error, perhaps? Platform: Windows 7 x64, SQLite 3.7.16.2 -- Григорий Григоренко _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
