Gnucash versions

[Keith Bellairs]

"never" is a little strong. I had a postgresql database corrupted by a crash
in a way that seemed pretty unrecoverable. So only use  the database backend
if you know how to take backups. (I had a current XML backup of the postgres
so I never even tried to fix the broken one :-))

Don't know if it was mentioned but the other benefit of the DB backend is
that it relies on the database's security. For those who want to password
protect their gnucash file, the databases provide a solution (sqlite, not so
much).

On Wed, Oct 12, 2011 at 12:56 PM, Derek Atkins <warlord at mit.edu> wrote:

> foxylady337 <hendry.michael at gmail.com> writes:
>
> > Thanks, Colin (and Bill and Yawar).
> >
> > I had the feeling I might be missing some new features by sticking with
> XML,
> > but this is obviously not the case.
>
> The only main feature you're missing is the "save on commit" capability
> of the SQL database, so you will never lose data by e.g. an application
> crash.
>
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
>
> -derek
>
> --
>       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>       Member, MIT Student Information Processing Board  (SIPB)
>       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>       warlord at MIT.EDU                        PGP key available
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> 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.
>