please. we can't continue to feed you the exact bugfix for your own application..... start with a small model, print what is passed back and adjust accordingly. Then extend to the "more complex" model and see what is the addition breaking. There are no limitations whatsoever
Il giorno lunedì 16 settembre 2013 01:36:17 UTC+2, 黄祥 ha scritto: > > yeah, you are right, your solution is work, i've tested it with the new > app, with the simple tables (only 2) and it work well, thank you so much, > but in my application that more complex it doesn't work. > i've already commenting my code that maybe affect the table in the model > (something like, label, required, represent, writable i commenting all) and > just use requires and default (for insert date), the result is same still > not work. > even test the simple after update that refer to it's own table is not > work. e.g. > > def __onvalidation_purchase_order(s, f): > purchase_order = s.select().first() > purchase_order.status = 'Purchase Order Authorized' > > db.purchase_order_header._after_update.append(lambda s,f: > __onvalidation_purchase_order(s, f)) > > btw, is there any exception, limitation for using _before and _after > callback in the database? > any idea what is the root cause for this problem? > > p.s. > tested update and delete from database administration and smartgrid (using > delete button and tick mark field in edit). all return the same result. > > 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
