> On Aug 31, 2017, at 10:35 AM, Matthew Pounsett <[email protected]> wrote: > > > > On 31 August 2017 at 13:33, Geert Janssens <[email protected]> wrote: > > While these solutions will work most of the time they all have the same risk: > if the snapshot is made while gnucash is updating the db, you end up with an > inconsistent db file. I don't know how well sqlite3 handles this so the risk > may be high or low. > > I've done a few spot-checks for consistency and never run into a problem. I > don't know this for certain, but it looks as if GnuCash is wrapping each > update in a transaction. If it is doing that, it would ensure that the data > written to disk is never inconsistent. >
Unfortunately the transaction protection mirrors GnuCash objects, so while plain GnuCash transactions will be correctly protected, business operations will do the business-table changes in one SQL transaction and the actual transaction in another. I think that Scheduled Transaction changes will similarly commit the template transaction separately from the rest of the SX. There are no doubt other cases. Regards, John Ralls _______________________________________________ gnucash-user mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
