On Mon, 2010-05-03 at 10:47 -0400, D. Richard Hipp wrote:
> Question 1: Are there any objections to this approach?
>
None here. My web-based applications (written in C) have just one call
to the existing open_v2 call so it is trivial to change them.
> Question 2: Are there other foibles that we could correct using
> sqlite3_open_v3?
>
// Allow delays for concurrent access
sqlite3_busy_timeout(hDB, 500);
That and foreign keys are the only non-default conditions that I need
to invoke after the call to open.
Chris Peachment
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
