OK, so that makes sense. What I see happening is creation of a journal file when i do the update/insert/delete statement each of which return SQLITE_OK. However, nothing is visible from an outside process (like sqlite3). If I understand you, this journal will be applied once the sqlite3_step finishes and I do the release on the prepared statement?
Is this correct? Igor Tandetnik <[EMAIL PROTECTED]> wrote: "Mike Johnston" wrote in message news:[EMAIL PROTECTED] > I'm running the 3.5.7 version now. My understanding was that if I > have a prepared statement and currently using sqlite_step to walk > through the results, the database was unable to commit a write. You cannot commit a transaction, but you can make updates. They will be committed at the end of the transaction (possibly an implicit transaction started when SELECT statement was issued). The transaction is promoted from read-only to read-write under the usual rules. > In my > case, I would be using the same connection. Would you explain more? Which part? > Also, what if same connection but different thread (assuming sqlite > compiled with multi-thread option turned on). I'm not sure about that, but I suspect it will also work. Why don't you try it and see? Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
