Sascha Sertel wrote: > While our long lived prepared statements are reset many times throughout > their lifecycle, there are several of them in use at the same time, and > probably never in a state where all of them are reset. The statements feed > a UI and are constantly refreshed, requeried, and reset based on user > actions. > > We actually hold a cache of prepared statements so we know which ones are > open, maybe as an experiment I could try calling reset on all of them and > see if that gives the checkpointer enough time to do its thing?
Would calling reset break your program? If not, you should call reset as soon as there is no more returned data (i.e., step returns SQLITE_DONE). Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
