> On Apr 3, 2018, at 1:06 PM, Colin Law <clan...@gmail.com> wrote: > > On 3 April 2018 at 19:40, Paul Neuwirth <m...@paul-neuwirth.nl > <mailto:m...@paul-neuwirth.nl>> wrote: > > ... > I am wondering, if no keep-alive is going to be implemented, if a > connection loss could be catched and connect again.. > the error message is: > "Unable to save to database." > > That is not unreasonable on connection loss. What happens after that?
I think that the session dies and given the current architecture that’s probably the right thing to do. GnuCash isn’t yet a database front end and the database connection code is tied into loading the database into memory. An outright crash or freeze would be bad, but restarting GnuCash or switching to a different book and switching back is at present the only safe course. Regards, John Ralls _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
