SQL BackEnd Clarification

[Russell Mercer]

I think it is rather important that this fact be noted prominently as a
warning on the website.  I am sure, as John said, that there has been
discussion through the development process of the various bugs related to
the SQL backend.  If you come to www.gnucash.org for the first time, find
the download, then look at the basic documentation, there is nothing
warning you that these other "storage options" contain potential for data
loss that is not there with the .xml version.  While it may not have been
hidden, I think it could be made more explicit.

That is my 2 cents.  Aside from this, please know the work you are doing is
very much appreciated.

Thanks,
Russell


On Tue, Dec 3, 2013 at 7:37 AM, Derek Atkins <warlord at mit.edu> wrote:

> Russell Mercer <rmercer206 at gmail.com> writes:
>
> > Derek,
> >
> > To be clear then, what you are saying is that even though the SQL
> backends
> > like SQLite, MySQL or PostgreSQL have been offered as equal storage
> options to
> > the basic .xml file, the reality is that a potential for data loss
> exists for
> > them that does not exist for the .xml storage?
>
> They have never been offered as "equal storage options".  They are just
> "storage options", but XML is still the default for a very good reason.
> But yes, the reality is that a potential for data loss exists for them
> that does not exist for the xml storage.
>
> >     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
>