Quick database question

[David T.]

Colin--

This solution raises one problem for the end user: when one uses Save as to a different format, THAT format becomes the default going forward. The user would have to know that if they wanted to continue using SQL, then they have to RE-save as SQL. That is counter-intuitive, and seems well-suited to a user not getting the behavior they expected. There is also the (exceedingly unlikely) possibility that the conversion back and forth might result in data corruption.

David

--- On Mon, 12/27/10, Colin Law <clanlaw at googlemail.com> wrote:

> From: Colin Law <clanlaw at googlemail.com>
> Subject: Re: Quick database question
> To: "Shane Litherland" <litherland-farm at bigpond.com>
> Cc: gnucash-user at gnucash.org
> Date: Monday, December 27, 2010, 3:37 AM
> On 27 December 2010 11:05, Shane
> Litherland <litherland-farm at bigpond.com>
> wrote:
> > ...
> > e.g. a bit of program that had
> >
> > IF database is postgres, THEN send "pg_dump with
> filename as current
> > file+timestamp+the-word-backup" to the postgres db,
> using user/login
> > that the user saved in their preferences or typed in
> the GUI for this
> > task; and save it in the location that user specified
> in prefs/GUI;
> >
> > OR, IF sqlite, then do same steps for it;
> > or ...etc
> >
> > and have a GUI that the user ticks which db they use,
> and other optional
> > bits as I alluded to above
> >...
> 
> Why bother with all this hard work?  What is wrong
> with File > Save
> Backup saving an XML format file?
> 
> Colin
> _______________________________________________
> 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.
>