File Format Decision

[Geert Janssens]

Hi Michael,

Here are a few considerations:

- If you prefer every entry you make is immediately saved to the backend 
store, sql is the better choice. It eliminates the need to press the 
save button from time to time. This is also the main reason sql was 
introduced into gnucash in the first place.

- If you wish to generate reports outside of gnucash (assuming the 
included reports don't fit your need), using an sql format is probably 
easier as you can write sql queries that operate directly on the data. 
One should only query for data this way, never alter data by the way.

I don't know of any other strong benefits of the sql backend.

Multi-user concurrent access is not possible with gnucash. Not with the 
xml backend and not with the sql backend. So this is no criterion to 
choose by.

The sql backend is not faster. It currently loads slower than the xml 
backend. And once the data is loaded gnucash does all queries in memory 
instead of from the database. Changes are written immediately to the 
database though at the same time as the data in memory is changed. In 
theory this makes each change operation slightly slower, but that's 
unnoticeable.

So the sql backend is not faster for large data sets either.

Lastly, the developers still consider the sql backend less well tested. 
All *known* issues with it are fixed. However from time to time a new 
corner case issue pops up that wasn't covered yet.

So in summary, while the word "sql" is suggesting "professional", 
"large-scale" and all other things associated with databases, unless you 
have a compelling reason to use it, the xml backend will do just fine. 
For my interpretation of "compelling reason", see the first two 
considerations.

Does that help to pick your preferred backend ?

Regards,

Geert

On Wednesday 21 September 2016 11:30:10 Fross, Michael wrote:
> Hello everyone,
> 
> I've fairly new using GNUCash, only a month or so and really enjoying
> it but have a quick question.
> 
> The website says that DB support is experimental, but I assume this
> has just not been updated and that there is no risk using SQL Lite. 
> I'd like to confirm my assumption.
> 
> Secondly, what is the general thinking on what to use when?  SQL Lite
> seems to me to be a better choice IMHO.  I understand I'll need to do
> the backups, but are there any other challenges?
> 
> I've looked around quite a bit but there is little decision criteria
> or options listed.  I did see large data files benefit from SQL, but
> it will be some time before I would consider my data file to be
> large.
> 
> I appreciate the opinions.
> 
> Regards,
> 
> Michael
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.