They are intent to be used to specify something before or after the delete... I mean even if there is no "pure" deletion occuring your record doesn't exist anymore for the end user once you "deleted" it even if versioning mechanism keep trace of it for the purpose of the audit trail integrity...
Do you have any issue related to how those callbacks operate in context of the version table web2py functionality? Richard On Thu, Mar 29, 2018 at 10:55 AM, Manuele Pesenti <[email protected] > wrote: > > Are actually _before_delete and _after_delete callbacks called on record > delete event even if on versioned tables? > > I mean on versioned tables records are just updated from is_active True to > False and not really deleted... right? So what is in thees cases the called > list of callback function? > > Thak you very mutch > > Cheers > > Manuele > > -- > 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. > -- 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.
