auth.record_versioning is just callbacks on steroids :P On Friday, January 10, 2014 5:12:58 AM UTC+1, Jayadevan M wrote: > > Great. You guys have thought about everything, huh? :) > > On Friday, January 10, 2014 1:50:36 AM UTC+5:30, Niphlod wrote: >> >> make your own "versioning" with database callbacks. >> >> http://web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#before-and-after-callbacks >> >> That way you can customize to whatever degree you like what happens when >> a row gets deleted/updated/inserted at any step. >> >> On Thursday, January 9, 2014 3:46:27 AM UTC+1, Jayadevan M wrote: >>> >>> A question about record versioning. Is it possible to have this ON and >>> still *not keep* deleted versions of the record in the original table? >>> 2 reasons - >>> 1) When there are tables with a number of deletes, the table will become >>> huge >>> 2) If we are using hand-written SQLs in many places, we have to remember >>> to add the filter to fetch only the valid records ( I am assuming when we >>> write our SQLs, web2py will not automatically add a filter). >>> >>>
-- 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/groups/opt_out.
