Op donderdag 19 april 2018 16:58:16 CEST schreef Alen Siljak: > > Sent: Thursday, April 19, 2018 at 3:47 PM > > From: "Derek Atkins" <warl...@mit.edu> > > To: "David T. via gnucash-user" <gnucash-user@gnucash.org> > > Cc: "alen.sil...@gmx.com" <alen.sil...@gmx.com>, "sunfis...@yahoo.com" > > <sunfis...@yahoo.com> Subject: Re: [GNC] .log files with sqlite backend > > > > So I don't see why you would want or need to replay logs with SQL. > > Is there a specific use-case here that I missed? > > Not really, except that the .log files are still created which is redundant, > as you just confirmed. The sql backend indeed does save all the changes > immediately and the Save button also becomes redundant. > The save button is permanently disabled when using an sql based book.
> So, from what I understand, the whole point of .log files is to help prevent > losing changes if there's a crash before the user clicks Save with an xml > book? > Yes. Geert _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
