and don't forget to call sqlite3_close() again after iterating and finalizing
the remaining prepared statements.
From: "SQLite List" <[EMAIL PROTECTED]>
Sent: Saturday, September 27, 2008 9:48 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Issue
Call sqlite3_close() first. If it returns SQLITE_BUSY, *then* iterate over the
statements list and close what statements remain. sqlite3_close() will cleanup
internal prepared statements for you and eliminate the error you're seeing.
From: junkJon
2 matches
Mail list logo
