Igor, I thought having a statement in progress or not finalized resulted
in SQLITE_LOCKED, not SQLITE_BUSY... but I have been searching for such
a condition anyway.
As to the second question below, the parameters bound each time are
different, thus the reset.
Igor Tandetnik wrote:
Dixon Hut
Dixon Hutchinson
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 statem
2 matches
Mail list logo
