Hiya, Firstly thank you for sqlite, it's proved to be a remarkably solid bit of software.
I recently noticed one interesting interaction -- or lack thereof -- between the default busy handler (registered via sqlite3_busy_timeout) and sqlite3_interrupt. Specifically, sqlite3_interrupt appears to have no effect on a statement that is currently trying to acquire a lock - at least not until the acquisition succeeds/fails. A quick look at the code suggested that the default busy handler indeed isn't checking the interrupted flag. I couldn't find anything in the changelog/archives on this topic, so my first question is whether the behaviour is by design? Or has it just fallen out this way? Thanks, -Rowan
