I dont' know the details of the busy handler. Not clear to me that it should sequentialize the requests.
Perhaps you're better off just using a flag that you could check between your commit;begin so that if there's a request in the queue you go process it before continuing. commit; if item_in_queue go_process begin; Did you eliminate the idea of using WAL mode? Michael D. Black Senior Scientist NG Information Systems Advanced Analytics Directorate ________________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Frank Chang [frank_chan...@hotmail.com] Sent: Tuesday, February 22, 2011 2:44 PM To: sqlite-users@sqlite.org Subject: EXT :Re: [sqlite] sqlite3_busy_handler I wanted to thank Michael D. Black and Simon Slavin for replying to my question. I was wondering how long the sqlite_busy_handler should sleep for before SQLite tries to access the datbase again. Our chief engineer was wondering whether the writing function could set an event when the write finished. The purpose of this event would be to notify the sqlite_busy_handler that the write finished so that the sqlite_busy_handler could use something like WaitForSingleObject before returning from the callback function. Thank you. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
