🚀 go-pugleaf

Bill Todd [TeamB] wrote:
> Isaac wrote:
> 
>> In fact debit and credit fields can be changed by user at any time, I
>> think I will need another trigger ? plz post any short examples of
>> triggers I did not use them before
> 
> In that case storing the running balance may be expensive since a
> change to the debit or credit amount in any row will change the balance
> for every subsequent row. Triggers and stored procedures are explained
> in the IB Data Definition Guide. It is impossible to explain the entire
> subject of triggers in a newsgroup message. After you read the Data
> Definition Guide chapters on stored procedures and triggers you can
> post any specific questions you have and someone will try to answer
> them.
> 

His post says cumulative balance -- that is easy. I think he means a 
"running balance" -- as you have assessed. That is not always easy as 
you have pointed out -- as it is sequence dependent.

Whenever you implement such a feature, they tend to "become wrong" 
exactly as you pointed out. So you always need to have routines which 
sequentially "fix" the running account balance -- for each entry. 
ACCPACC in it's DOS days definitely had those routines built in -- as 
did many other accounting systems.

It is usually easier -- on a fast server -- to calculate the balance to 
a required point via SQL queries.

If a cumulative balance is required -- I would suggest a stored 
procedure which runs a calculation routine on demand. It is 
procedural/sequential after all.




-- 
Will R
PMC Consulting