[GNC] Auto commit with auto save?

[Adrien Monteleone]

David,

I didn't notice when I replied, that this thread broke (at least for me) 
and there were more detailed replies.

Now that I see what the OP was encountering, I agree, SQL won't be a 
solution for anything not committed.

Other than this special case, I'm not sure it would be a good idea to 
auto-save uncommitted transactions. (especially if they don't balance 
yet) I'd hazard some folks rely on that current behavior.

I do agree some sort of visual indication as to which open registers 
have uncommitted transactions would be helpful, as would the warning 
message being more specific to avoid a guessing game.

And certainly, the OPs original goal might be better implemented within 
the GUI so as to avoid the issue entirely, as it seems the cron job is a 
work around. (thus it seems the problem isn't not auto-saving or 
auto-committing transactions on exit, but rather the lack of ability to 
schedule price updates)

Regards,
Adrien

On 5/10/23 11:02 PM, David T. via gnucash-user wrote:
> Adrien,
> 
> The issue as stated is specifically the loss of an uncommitted transaction, so an SQL back end won't help with that. If, however, that open transaction prevents an entire session from being saved, then your suggestion merits attention. I personally don't know about that, though; the OP didn't mention.
> 
> ⁣David T. ​