Version Migration

[Geert Janssens]

On donderdag 31 augustus 2017 19:08:28 CEST Matthew Pounsett wrote:
> On 31 August 2017 at 12:27, John Ralls <jralls at ceridwen.us> wrote:
> > It also doesn't make backups, so unless the user does there's no way to
> > roll back to an earlier state. Since all changes are immediately written
> > to
> > storage there's also no way to abandon a bunch of changes by quitting
> > without saving.
> > 
> > I'm accomplishing that part by writing the sqlite3 file to Dropbox, which
> 
> provides file history (so I can roll back if necessary) and takes care of
> replicating the data between my desktop and laptop, provided I'm careful
> never to run the app in both places at the same time.
> 
> The backups could be automatically accomplished with other storage that
> provides a versioned backup... MacOS's Time Machine would do the trick, for
> example.  ZFS doesn't work particularly well on Linux (it's a Solaris and
> BSD thing), but I imagine there's some other option for obtaining snapshots
> there, and likewise I assume Windows would have a similar feature.

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.

Geert