2.4.0, what's left to do

[John Ralls]

On Nov 20, 2010, at 8:44 AM, Yawar Amin wrote:

> Hi,
> 
> On 2010-11-19, at 22:59, John Ralls wrote:
> 
>> 
>> On Nov 19, 2010, at 5:18 PM, Yawar Amin wrote:
>> 
>>> […]
>>> 
>>> * New SQL backend secures your data and makes it more accessible with reporting tools
>>> 
>>> […]
>> 
>> 
>> I think we are (and should) leaving the default as XML for 2.4. There isn't a substantial benefit for the ordinary user
>> to switch to sql until we (1) rewrite (or replace) qof so that it doesn't need to lock the whole database and (2) rework 
>> the backend to make better use of sql's data integrity features (which means moving those functions out of qof).
> 
> OK, so this database backend is a start in the right direction, but it’s not exactly using the full benefits of SQL’s  transactional model. I want to capture the headliner benefit of this release for the user in a single, memorable, line. The way I see it, the most immediate benefit is that the user can query the SQL with their own tools, be it Crystal Reports, JasperReports, or other custom tools.
> 
> Can anyone put this more succinctly?
> 

It's also easier to share access if one uses MySql or Postgres, and there's less worry about saves because edits are committed immediately instead of being logged and saved at intervals, as with the XML backend.

How about something like this:

Optional SQL backends, using Sqlite3 files or connections to MySql or Postgresql servers. While Gnucash is still not a database-oriented application, using a SQL backend offers access to Gnucash data with third party SQL tools (especially report writers like Crystal Reports or JasperReports) and immediate saving of every edit. Using a SQL server simplifies access from more than one computer (but not at the same time). 

It's a bit longer than one line. Is it concise enough for your "what's new" article?

Where is "what's new", anyway?

Regards,
John Ralls