Setting up gnucash to use postgesql back end - close but no cigar ...

John Ralls jralls at ceridwen.us
Tue Mar 10 20:08:32 EDT 2015


> On Mar 11, 2015, at 2:04 AM, Jan Steinman <Jan at ecoreality.org> wrote:
> 
>> From: John Ralls <jralls at ceridwen.us>
>> 
>> ... once we switch to using SQL as the internal data representation...
> 
> be_still(heart);
> 
> I *really* want an inter-operable SQL back-end. I can almost taste it.
> 
> I looked at the current data model (in MySQL), and it looks like... it's not really a data model. More like a general data dump (slots table). Perhaps I could be of assistance.

Hmm. Interoperable with what?

Yes, it's true that the current schema is just a persistence of GnuCash's internal representation. That's pretty standard for business applications if my reading of Fowler's "Patterns of Enterprise Application Architecture" is correct. In any case it's not likely to change: All of the business logic is likely to stay in GnuCash rather than move to the database.

Regards,


More information about the gnucash-user mailing list