Re: [sqlite] sqliteDefaultBusyCallback and HAVE_USLEEP

2020-02-26 Thread Peter Kolbus
> On Feb 26, 2020, at 5:53 AM, Graham Holden wrote: > > Wednesday, February 26, 2020, 11:15:14 AM, Richard Hipp > wrote: > >>> On 2/25/20, Peter Kolbus wrote: >>> I noticed that sqliteDefaultBusyCallback() seems to depend directly on the >>> OS (behave differently based on SQLITE_OS_WIN||H

Re: [sqlite] sqliteDefaultBusyCallback and HAVE_USLEEP

2020-02-26 Thread Graham Holden
Wednesday, February 26, 2020, 11:15:14 AM, Richard Hipp wrote: > On 2/25/20, Peter Kolbus wrote: >> I noticed that sqliteDefaultBusyCallback() seems to depend directly on the >> OS (behave differently based on SQLITE_OS_WIN||HAVE_USLEEP). Since the >> underlying primitive, sqlite3OsSleep(), act

Re: [sqlite] sqliteDefaultBusyCallback and HAVE_USLEEP

2020-02-26 Thread Richard Hipp
On 2/25/20, Peter Kolbus wrote: > I noticed that sqliteDefaultBusyCallback() seems to depend directly on the > OS (behave differently based on SQLITE_OS_WIN||HAVE_USLEEP). Since the > underlying primitive, sqlite3OsSleep(), actually uses the VFS to sleep, and > unixSleep() also has a roundup to w

[sqlite] sqliteDefaultBusyCallback and HAVE_USLEEP

2020-02-25 Thread Peter Kolbus
I noticed that sqliteDefaultBusyCallback() seems to depend directly on the OS (behave differently based on SQLITE_OS_WIN||HAVE_USLEEP). Since the underlying primitive, sqlite3OsSleep(), actually uses the VFS to sleep, and unixSleep() also has a roundup to whole seconds when HAVE_USLEEP is not d