Thanks Igor for the quick response; bless your soul. So I will fire away a few more questions surrounding this :)
1. If there is a commit already in progress and I start another begin/commit block on this connection, will this begin or commit fail? If so, with what error? 2. If yes to (1) then is there a way to queue the commits so that the 2nd does not start until the first one is over? 3. If for some reason, this for loop (mentioned in my original question) does not add any statement to be executed, will commit fail with this error? In other words, can there any empty commit? On Mon, May 11, 2009 at 5:17 PM, Igor Tandetnik <itandet...@mvps.org> wrote: > "Blasfamous Tshirts" > <blasfam...@gmail.com> wrote in message > news:ca0e99280905110444x26c5499fn51cf794932a5d...@mail.gmail.com<news%3aca0e99280905110444x26c5499fn51cf794932a5d...@mail.gmail.com> > > Under what scenarios can commit fail with this error "no active > > transaction"? > > > > I have a BEGIN just before a for loop and a COMMIT after that, and it > > fails with this error. > > Something inside that loop failed and caused rollback. > > Igor Tandetnik > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
