Re: [sqlite] multiple outstanding sqlite3_stmt objects

On 19 Dec 2012, at 1:21am, Larry Brasfield wrote: > Is there any reason not to do this? Don't do it if one statement is a SELECT and another statement interferes with the normal way that _step() would step through the results. Although the API will not immediately

Re: [sqlite] multiple outstanding sqlite3_stmt objects

On 12/18/2012 8:21 PM, Larry Brasfield wrote: At http://www.sqlite.org/c3ref/stmt.html , there is a weak implication that SQLite may expect single sqlite3_stmt objects to exist for a connection. Not sure what led you to believe this. You definitely may have multiple prepared statements on one

[sqlite] multiple outstanding sqlite3_stmt objects

At http://www.sqlite.org/c3ref/stmt.html , there is a weak implication that SQLite may expect single sqlite3_stmt objects to exist for a connection. The pattern I intend to follow instead of the one shown as "life of a statement object goes something like this" is: 1. Create sqlite3_stmt #1