yes, the new tables same for all which is base on detail_coa.
the idea is to separate it is base on the case 
e.g.
user input data on chart_of_account table e.g. :
-cash
-bank a
-bank b

the same thing goes for account table that automatically create 
chart_of_account table to maintain the data of the account which is goes to 
"account payable" + str(account.name) or "account receivable" + 
str(account.name) will be calculate for their balance AP or AR

if i'm not separate it into several table when user posting the data the 
calculation to calculate the *balance* field, base on previous record in 
*balance* field on the same table will be messed up

in the past i just use after insert callback for that to update the value 
of balance, but here again we met the condition if there is human error, so 
we can not trace back and update to the correct value, because all of the 
data is updating the balance field without any single history transaction 
track on table, which is i think the best is to store it to separate table 
for that

currently, the new table for separate table, i think when user have a 
mistake before they posting the data, they can correct it in their 
transaction and automatically update the new table base on their coa's data 
in transaction. if they already posting it, it simply just unpost, correct 
and posting again

the problem i met right now is when user update the coa data, how can it 
affect the table created, e.g. change the coa name, i can handle for after 
insert or before delete case, but for update, too many scenario will 
happen. 

so not sure if this best practice or not, in terms of performance or 
complexiity system, any ideas or correction to do it, using web2py way are 
welcome

thanks and best regards,
stifan

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to