Re: [sqlite] sqlite3_busy_timeout() not working with 3.0.x?

2004-09-03 Thread Matt Wilson
On Fri, Sep 03, 2004 at 09:20:05AM -0400, D. Richard Hipp wrote: > > It does if you put the timeout on pDb2. You're right. That's what I get for hacking up test cases at 1 AM. Thanks, Matt

Re: [sqlite] sqlite3_busy_timeout() not working with 3.0.x?

2004-09-03 Thread D. Richard Hipp
Matt Wilson wrote: On Thu, Sep 02, 2004 at 08:24:21PM -0400, D. Richard Hipp wrote: If you do separate sqlite3_open() calls for each statement, the behavior will be more along the lines of what you expect. Attached test case still doesn't seem to wait. It does if you put the timeout on pDb2. --

Re: [sqlite] sqlite3_busy_timeout() not working with 3.0.x?

2004-09-02 Thread Tito Ciuro
Hello Matt, On Sep 2, 2004, at 19:46, Matt Wilson wrote: I would expect for sqlite3_busy_timeout(db, 3); to make the step() on statement 2 wait 30 seconds before returning, but it returns immediately. I believe sqlite3_busy_timeout() is called whenever sqlite3_step() returns SQLITE_BUSY. In