It's possible, but not if they're doing what yours are. Namely the problem here is not that you have a before and after update callback. The problem is your __after_update_order. Your __after_update_order updates table *order* which triggers __after_update_order again. This would be ok if you had a condition that would terminate the recursion which you don't,
Lets see what happens when s.update(notes='test') runs. This is an update where 'is_active' is not in *f* so it will trigger s.update(notes='test') again. And again. And again. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
