Dixon Hutchinson
<sqlite-491LjFE5FnHkPponyUOvwgC/[EMAIL PROTECTED]> wrote:
The basic problem is that I am getting SQLITE_BUSY on a call to
sqlite3_exec where the SQL passed is simply "COMMIT;"
Most likely, you still have a statement in progress that has not been
reset or finalized.
3. Bind parameters to a previously prepared statement to
perform a SELECT.
4. call sqlite3_step on the statement
5. call sqlite3_column... to retrieve the data from the select
6. call sqlite3_reset on the statement
7. perform steps 3-6 around 5 times. The loop is terminated
when sqlite3_step returns SQLITE_DONE.
This doesn't make sense. If you call reset after every step, you are
going to retrieve the first row over and over, and will never get
SQLITE_DONE.
Igor Tandetnik
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
