Hi,

I'm converting SQLite2 code to SQLite3. It looks to me like the
sqlite3_busy_handler() and sqlite3_busy_timeout() don't do anything.
At least not anything useful. At least not when using the new API with
sqlite3_step() and friends.

Is that true? Do I have to catch SQLITE_BUSY from the _step() etc.
calls myself and call an appropriate busy handler?

All in all, I wonder why the old functions were left in the API if
they don't work properly. But maybe I've overseen something.

Don't get me wrong: I like the new API a lot :-)

-- Gerhard

Attachment: signature.asc
Description: Digital signature

Reply via email to