In the sample code I did not indeed. But in the actual code that i'm using, the prepared statement used was part of bulk insert surrounded by begin transaction/ commit transaction. I was reseting the stmt before it was used inside of transaction and not after, so it caused a problem.
this is what i had: begin transaction loop of reset step commit changed it to: begin transaction loop of step reset commit I assumed that commit would take care of sync, but because my statement was never finalized/reset after last use, it didn't it seems.. Thanks, Yuriy On Jun 25, 2013, at 6:39 PM, Richard Hipp <d...@sqlite.org> wrote: > On Tue, Jun 25, 2013 at 6:32 PM, Yuriy Stelmakh <yuriy...@gmail.com> wrote: > >> Thank you! that did the trick. Its interesting that even though you >> can commit a transaction, the cache sync doesn't happen until you >> finalize or reset all you statements. I wish this was documented >> somewhere better! >> > > > No, you completely misunderstood what I said. > > You never issued an explicit COMMIT. And you had a read operation in > progress (because you never finished the count(*)) which means that no > autocommit would happen either. Hence, your transaction was never > committing. > > This has nothing whatsoever to do with caches or syncing. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > 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
