Getting 2.4 Released - Yes!

Phil Longstaff plongstaff at
Wed Oct 20 10:40:39 EDT 2010

This strikes me as a *very* reasonable approach to take.  I happen to use the 
SQL backend for my daily use, but then again, I guess I'm supposed to eat my own 
dog food.  Maybe for now, the Save As dialog should be modified to remove the 
SQL backends, and an "Export to SQL" menu entry should be added to include 
them.  This would leave "Open", "Save As" and "Export to SQL" all using the same 
basic dialog box, and the only difference between Save As and Export to SQL 
would be in the items in the storage type dropdown list.

I used to be a hypochondriac AND a kleptomaniac. So I took something for it.

From: Graham Leggett <minfrin at>
To: AshokR <ashok at>
Cc: gnucash-devel at
Sent: Wed, October 20, 2010 10:23:21 AM
Subject: Re: Getting 2.4 Released - Yes!

On 20 Oct 2010, at 12:17 AM, AshokR wrote:

> By this approach, it is a win-win for both users and developers. The users
> get the option to save in  relational database formats to use third-party
> reporting tools and integrate with other applications. And the developers
> get to bake SQLite3 integration code, for a possible future switch to that
> format as 'native'.


I won't be trusting the SQL stuff as a primary source for my data for a long 
time, but exporting it to a SQL database so I can query against it would be very 


gnucash-devel mailing list
gnucash-devel at

More information about the gnucash-devel mailing list