Pull Request Test Coverage Report for Build 16337968461

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 70 unchanged lines in 11 files lost coverage.
• Overall coverage decreased (-0.02%) to 65.74%

Totals
Change from base Build 16336414032:	-0.02%
Covered Lines:	127435
Relevant Lines:	165235

💛 - Coveralls

I doubt this change will have any effect.

We currently invoke sqlite3_busy_handler() to set up busyHandler as the, well, busy handler, and this callback always returns non-zero, which means that, regardless of the timeout, sqlite3_step() will never return SQLITE_BUSY.

A first change, for this PR to have a chance to be useful, would be to change the callback to eventually return 0 if the number of times it has been invoked reaches a certain limit, and then the call to sqlite3_busy_timeout() becomes unnecessary.