Setup mysql

[John Ralls]

On Feb 3, 2011, at 10:23 AM, Kurt Amesbury wrote:

> Thanks for the info.
> 
> I'm not familiar with sqlite3, but am familiar with mysql.  Any downside to sqllite3 that you know of?
> 
> Kurt
> 
> On Feb 3, 2011, at 13:09 , John Ralls wrote:
> 
>> 
>> On Feb 3, 2011, at 9:55 AM, Kurt Amesbury wrote:
>> 
>>> In setting up gnucash, the options for backend storage didn't include mysql.  The only options were sqlite3 and xml.
>>> 
>>> Is this feature not yet implemented?
>>> 
>>> Gnucash version: 2.4.0
>>> OS: MacOS 10.5.8
>> 
>> From the release notes:
>>> The only libdbi module included is for SQLite. If you need either the MySQL or Postgresql modules, you will have to build them yourself and install them into Gnucash.app/Contents/Resources/lib/dbd. For instructions, see MacOSX/Quartz.
>> 
>> The instructions for building the drivers are at http://wiki.gnucash.org/wiki/MacOSX/Quartz#Building_Libdbi_Drivers

Depends on what your goals are. Sqlite3 is a local, no-admin Sql database that keeps everything in a single file on a local disk.   If you want Sql so that you can independently query your Gnucash database, then Sqlite3 is probably the right solution as it incurs much lower overhead -- both in system and user resources. On the other hand, if you already have a MySql installation, are comfortable administering it (or have an employee who is), have it set up for backups, and want to use it to access your Gnucash data from more than one computer (not simultaneously, Gnucash can't safely do that), then MySql might be a better choice.

Regards,
John Ralls