Default save-as file format: Rather stick to XML?
plongstaff at rogers.com
Mon Nov 2 11:05:14 EST 2009
Please include the gnucash-devel mailing list.
I've been using the sqlite3 backend for my home use. However, since I don't use the business features extensively (I have a bit when I was doing some contract work), there are some issues I don't run into. There are still some issues (see the SQL Backend category for GnuCash in bugzilla.gnome.org that need to be fixed before it is ready for production use.
From: T. Howell-Cintron <lists at kathera.com>
To: Phil Longstaff <plongstaff at rogers.com>
Sent: Mon, November 2, 2009 10:51:46 AM
Subject: Re: Default save-as file format: Rather stick to XML?
Phil Longstaff wrote:
> One thing that the 2.3.X series has done is flush out some of the sql backend problems. I don't think that would have happened if it had just stayed on trunk, limited to those who build trunk themselves. I think the gnucash website does need some work to make the latest stable version (2.2.9) *much* more visible vs the unstable releases.
I concur - as a new GnuCash user it was so much easier to locate and download the unstable release than the stable one, and it wasn't until I tried to load my data-set in to a pre-installed (Fedora) stable release that I realized the mistake.
> I'm not yet ready to switch back to the XML backend but I won't rule that out.
Is the sqlite3 back-end ready for production use? I'll happily stick with XML because it's more portable but if sqlite3 is ready I'd be game for using it more often.
More information about the gnucash-devel