Hi, I'm probably missing something obvious since I don't see anyone asking this but here it goes...
I want to archive a db record but, at a later date, I may want to unarchive it, i.e. make it current again and I'm not sure I understand how to do that coherently - I have record versioning enabled - I can see that when I "delete" a record in table "abc", its "is_active" field is set to False and the abc_archive table gets a new entry for the deleted record But, if I now want to reverse the process, i.e. make the record current, what do I need to do (and leave the db in a state where, if I later re-archive that record, things are consistent? ) - Only set "is_active" to true? - What about the records in the archive table? Delete/modify those records? - if I later re-archive that record, I need things to be consistent Ideally, I'd like a ongoing modification history - record was originally created 3 years ago, archived last year, re-activated 3 months ago and re-archived yesterday... Thanks, Jim -- 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.
