Hi, This problem was evoked on the list. sqlite3_exec do not catch SQLITE_BUSY on the sqlite3_step. If you want to continue to use the sqlite3_exec properly with busy handler, you can copy and modify the method stored in src/legacy.c. I can send you my modified version if you need. It seems, to me, the only conversion problem between v2 and v3.
Cheers, Thu, Oct 21, 2004 at 03:51:10PM +0200: Gerhard Haering wrote: > 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 -- Guillaume FOUGNIES
