GWB wrote > Unless you are willing to spend some time learning various sql query > and dbase commands and functions, I would stick with SQLite and make > snapshots (if your file system allows it) or frequent backups.
I'm also doing this manually with the SQLite backend. I wrote a small Python script that compacts the database, compresses it using LZMA algorithm, and creates a copy in the backup folder. There I keep ~50 recent files, manually copying the last one every month to a long-term backup directory. While the backup scheme implemented for the XML storage is nice and convenient, I don't think it would be necessary to try to accommodate all the different backends in that regard. I can only thank the developers for making it so simple as to having one file with all the data when using SQLite backend. That way I can implement any backup scheme I like. On Linux there are some nice automatic backup options available but I stopped using that after writing the above script, which I now use on all the platforms where I use GnuCash. -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html _______________________________________________ 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.
