🚀 go-pugleaf

Ok guys, but I saw another solution used in the "Peachtree complete 
accounting" package it uses the client to update the "running balance".

First no direct change in the window the user have to open another 
window to make the update,

Then a global flag set for example "balance_need_update = true" and when 
the user close the window and the the balance window get the focus a 
small progress bar appear indicating of fixing the balance.

this scenario did not occur if no change happened and also controlled by 
the current selected period of the year (3 months) and the update occur 
from the modified record down to the end of the selected period so it 
take few seconds.

it is also in my opinion more light to do the calculation on the client 
with executing SQLs than using triggers and procedures on the server in 
case of 50 user using the software.

What do you think ?