On Jan 9, 2014, at 10:10 AM, Roger Binns <rog...@rogerbinns.com> wrote:
> The default busy handler (see sqliteDefaultBusyCallback in source) sleeps
> for these amount of milliseconds:
>
> { 1, 2, 5, 10, 15, 20, 25, 25, 25, 50, 50, 100 };
>
> However on non-Windows if you do not have HAVE_USLEEP defined then it
> sleeps with a granularity of one second. The blocking thread could have
> finished after 10ms, but you'll still be stuck in the busy handlers for
> another 990ms.
>
> Simply ensure HAVE_USLEEP is defined when building sqlite3.c. Or add your
> own busy handler that sleeps for sub-second amounts of time.
I was more interested in the scenario than the solution -- but I probably would
have missed this simple fix and done something elaborate and stupid, so thank
you very much!
-- Ward
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
