Change storage format of existing data

David T. sunfish62 at yahoo.com
Sun Jan 29 11:40:50 EST 2017


Rich,

David C.’s comments are entirely on point with regard to the relative value of the SQL back end; the SQL back end has been a long, slow development process that is still not to a point where it can be recommended for basic general use. This is why the support for it has not been written to date—and why most of what is out there is exceedingly sparse.

David C. goes on to refer to a different, but related thread, in which I raised the possibility of creating documentation regarding the SQL back ends. Such documentation is a little late for your needs, but might help others navigate this issue in the future. I made the proposal in part because of the questions you have raised in this thread.

David T.

> On Jan 29, 2017, at 9:29 PM, David Carlson <david.carlson.417 at gmail.com> wrote:
> 
> I am not a developer, just a user that knows enough to be very dangerous...
> 
> From my perspective, the SQL back-ends have very little value beyond exposing the data to some limited SQL queries.  The commonly known features of most SQL databases like multi-user access and loading only the data needed rather than the entire database are yet to be implemented.  The developers warn that data should only be saved through the GnuCash front end because relationships are not defined in the database but in the GnuCash code.  Back-ups are not implemented at all, unlike the XML backups, which still do not back up user configurations.
> 
> I agree with David T, however, that it is time to lay the cards on the table so users can see the advantages, disadvantages and proceed with due caution if that is what they want to do.  For myself, I am staying with XML until the SQL structure is developed to the point of permitting multi-user access, partial data loading and data writes via other front-ends.
> 
> David C
> 
> On Sun, Jan 29, 2017 at 9:50 AM, David T. via gnucash-user <gnucash-user at gnucash.org <mailto:gnucash-user at gnucash.org>> wrote:
> Rich,
> 
> In addition to --enable-dbi, you need to install the libdbd libraries (libdbi-dbd-mysql, libdbi-dbd-postgresql and libdbi-dbd-sqlite), which John implied.
> 
> David
> 
> > On Jan 29, 2017, at 8:43 PM, Rich Shepard <rshepard at appl-ecosys.com <mailto:rshepard at appl-ecosys.com>> wrote:
> >
> > On Sat, 28 Jan 2017, John Ralls wrote:
> >
> >> apt-get install libdbd-sqlite3 libdbd-mysql libdbd-pgsql
> >
> > John,
> >
> >  Thanks for the above. Looking for a slackware solution led me to
> > <https://wiki.gnucash.org/wiki/Slackware#Requirements <https://wiki.gnucash.org/wiki/Slackware#Requirements>>, specifically to the
> > section "Slack 14.1 + GnuCash 2.6.X" where I learned that the SlackBuild
> > script requires --enable-dbi as a configuration option.
> >
> >  That option is not in the default script (neither is --disable-dbi), so I
> > added it, rebuilt, and reinstalled 2.6.15.
> >
> >  With my existing file there's still no postgres option displayed in the
> > Save as dialog.
> >
> >  Are data file format options available only when a file is created and not
> > retroactively?
> >
> > Regards,
> >
> > Rich
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org <mailto:gnucash-user at gnucash.org>
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user <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.
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org <mailto:gnucash-user at gnucash.org>
> https://lists.gnucash.org/mailman/listinfo/gnucash-user <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.
> 



More information about the gnucash-user mailing list