WHY use anything other than an XML backend?

[Keith Bellairs]

Also, you can password protect your database. Users have asked how to
password protect the XML and learn that it is not a supported feature. Move
to postgres and there you have it.

On Tue, Apr 19, 2011 at 4:13 PM, Geert Janssens
<janssens-geert at telenet.be>wrote:

> On dinsdag 19 april 2011, gbguy wrote:
> > John,
> > Thanks for the info.  As I said before, not all the GnuCash users are
> > developers, so keep them in mind when you make your announcements.
> >
> > Later today I'm going to make an entry in the FAQs about the use of XML
> and
> > SQL.  You can change it if you don't agree with what I said.
> >
> > --
> > View this message in context:
> >
> http://gnucash.1415818.n4.nabble.com/WHY-use-anything-other-than-an-XML-ba
> > ckend-tp3460934p3461366.html Sent from the GnuCash - User mailing list
> > archive at Nabble.com.
> > _______________________________________________
> > 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.
>
> Another advantage of the sql backend is that it saves instantly, so you
> have
> less risk of data loss (except for the issues with online banking John
> mentioned).
>
> As far as I remember, that was the primary motivation to introduce an sql
> based backend in the first place. The tech is still fairly new in GnuCash
> though and should probably still mature some.
>
> Geert
> _______________________________________________
> 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.
>