No. By using auth.signature a deleted field is still deleted. auth.signature simply add extra fields. If you use a signature AND you auth.enable_record_versioning(db) then records are never deleted because it keeps all the history.
On Wednesday, 9 December 2015 23:48:45 UTC-6, at wrote: > > Thank you Massimo. > > One quick question: When we use auth.signature, and then delete records in > a table, they are marked as deleted but they are not actually deleted from > the database. What is the recommended way to delete such records from the > database? > > Best Regards, > AT > > On Thursday, 10 December 2015 09:35:15 UTC+5, Massimo Di Pierro wrote: >> >> It is well hidden >> n >> >> http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer?search=auth.signature#Table-inheritance >> >> On Wednesday, 9 December 2015 00:17:17 UTC-6, at wrote: >>> >>> Hi, >>> >>> I am unable to find explanation of how does auth.signature works >>> anywhere including web2py documentation. I can see that after adding it to >>> a database table definition, it starts maintaining a revision history of >>> the records. I've also seen that deletion of a record does not actually >>> delete it from the database but it is marked as inactive; what is the >>> recommended way or configuration that allows me delete the *inactive* >>> records from the database? >>> >>> Thanks, >>> AT >>> >> -- 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.
