Gnucash file is getting long!

Adrien Monteleone adrien.monteleone at gmail.com
Tue Jun 20 11:45:23 EDT 2017


Geert,

Is this supposed to be the case for SQLite3 also? Because I’m still seeing periodic saves based on my preference setting. And I had a crash last week that resulted in lost changes since the last save.


Regards,
Adrien

> On Jun 20, 2017, at 3:14 AM, Geert Janssens <geert.gnucash at kobaltwit.be> wrote:
> 
> There are no automatic saves in the sql backend any more. Or rather every change you make is saved automatically and immediately. So the autosave delaus you experience on the xml backend don't happen when using sql. The initial loadtime on the other hand turns out to be slower. This should improve when gnucasj becomes a real db application.
> 
> David Carlson <david.carlson.417 at gmail.com> schreef op 17 juni 2017 22:39:44 CEST:
>> If the MySql format data file is not on the main hard drive but a) on a
>> USB
>> 2.0 or 3.0 key, b) on another computer accessed by Wi-Fi or Ethernet,
>> c) on
>> a cloud server.
>> 
>> Would the MySql database format be faster than the compressed XML in
>> any of
>> the above scenarios, particularly when periodic automatic saves are
>> kicking
>> in.?
>> If GnuCash is remotely driven from another computer via ssh or Remote
>> desktop are there any significant differences between the data formats
>> for
>> those scenarios?
>> 
>> David C
>> 
> 
> Sent from my smartphone. Please excuse my brevity.
> _______________________________________________
> 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.



More information about the gnucash-user mailing list