As 4.9 does abort ungracefully from time to time, I grow weary of reentering my unsaved transactions. I suggest that you post them to a new sort of log file as I go, so I do not have to save megabytes of almost duplicate files so often to avoid this. Of course, if I leave the cursor on a modified line, I still might lose that line, unless you can log that along with its state when I change tabs. (Maybe I should be warned when I change tabs that I left an uncommitted transaction, not later when I save?) When the app starts, it can check the file and replay. When there is a save and the normal files are closed or flushed to disk, the new log file can be truncated. It'd be very much like an RDBMS log. And perhaps a way to allow us to save less often? _______________________________________________ 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.
[GNC] Post crash recovery log file suggestion
David G. Pickett via gnucash-user Sat, 15 Jan 2022 11:11:50 -0800
- [GNC] Post crash recovery log file sugge... David G. Pickett via gnucash-user
- Re: [GNC] Post crash recovery log f... john
- Re: [GNC] Post crash recovery l... David Carlson
- Re: [GNC] Post crash recove... David G. Pickett via gnucash-user
- Re: [GNC] Post crash recovery l... David G. Pickett via gnucash-user