Can you show your Auth setup code. Merely adding auth.signature to a table should not enable record versioning nor result in deleted records merely being marked inactive. Rather, you must explicitly enable record versioning. If you enable record versioning and the versioned table contains an "is_active" field, then deleted records will not be deleted but instead marked as inactive. If you want record versioning but do not want to preserve deleted records, then you can simply make sure there is no "is_active" field in the table. You won't be able to use auth.signature as is, as it includes the "is_active" field, but you could do something like this:
signature_fields = [f for f in auth.signature if f.name != 'is_active'] And then add signature_fields to your tables. Anthony On Wednesday, December 9, 2015 at 1:17:17 AM UTC-5, 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.
