On 2/9/16, olivier vidal <vidal.olivier at mac.com> wrote: > > - One thread writes > - While this thread wrote, another thread requests to write. Of course, > a "busy" error is generated, this is normal. But until the error is > generated, all threads in the application are frozen during the sqlite > timeout! > > I tried using "sqlite3_progress_handler" with multiple values.
The interface that governs the timeout is "sqlite3_busy_handler()". Perhaps you can modify its callback to yield to another thread, rather than simply sleeping. Or just set the timeout value to zero and deal with retries manually in your application. -- D. Richard Hipp drh at sqlite.org
