Hi Paul, Interesting idea :) A bit hacky but that's something to be considered perhaps. However, killing the application usually implies action being taken from outside of the app. I don't believe such things are possible on i.e. iOS (one of the platform supported by our app), though I might be wrong.
Cheers, Albert ________________________________________ Od: sqlite-users-bounces at mailinglists.sqlite.org <sqlite-users-bounces at mailinglists.sqlite.org> w imieniu u?ytkownika Paul Sanderson <sandersonforensics at gmail.com> Wys?ane: 27 kwietnia 2016 13:54 Do: SQLite mailing list Temat: Re: [sqlite] Controlling of check-pointing of WAL Dbs Can you kill the process rather than shut down your application? If the last connection doesn't get shut then the WAL will remain and will be in opened (but not played) when the DB is re-opened. Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 27 April 2016 at 12:38, Albert Banaszkiewicz <Albert.Banaszkiewicz at tomtom.com> wrote: > Hello. > > I am new here, thus I would like to apologize in advance if the question I am > going to rise was already asked in the past. > > I am using SQLite 3.11.1 (actually it is a NDS consortium customized version > based on it). > > According to documentation, in case of WAL mode enabled databases, final > check-pointing is being done when the last connection to DB is about to be > closed. > > We are running into the scenario, where we would like to have a complete > control over the moment when check-pointing happens. This is easy in case of > auto-check-pointing, where it can be completely disabled or customized (via > hooks). > However, it is possible that during the component life-time there is going to > be no 'appropriate' moment to schedule it and if the user powers device down, > we still want to avoid it since modern OSes typically expect running > applications to terminate within the specified (several seconds usually) time > intervals. Of course, we don't want to loose any data contained in the WAL > journal as well and ideally, we would like to be still able to schedule > check-pointing in the 'appropriate' time after reboot. > > So finally, the questions: > > 1. Is there a way to control (i.e. disable) check-pointing happening at DB > closure ? (personally, I could not find anything like this in the code but > perhaps I missed something) > 2. If not, are there any plans to introduce it ? Or is it not feasible at all > ? > > Thank you in advance, > Albert > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users