On 08/31/17 13:35, Matthew Pounsett 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. > _______________________________________________ > 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. >
Since my company is small, I'm sticking with the legacy gnu system, for now. That's the permanently offline system I'm in the process of migrating too. Is anyone basically using a USB stick for all records? If so, can you just plug that USB stick into any of several different (but same version of gnucash), make changes and store all records on a usb 2 or 3 device? Then copy usb-stick for backups? Like others, I am curious to track the database progress, as well as running gnucash on a cluster. Anyone running many instances of GNUcash on containers, alpine or just a bunch of VMs? I'd be most interested in those experiences too. Projects of such multiplicative offerings of gnucash I could follow? James _______________________________________________ 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.
