check this out. http://web2py.com/books/default/chapter/29/06#Record-versioning
On Tuesday, March 12, 2013 7:02:09 PM UTC+1, Lamps902 wrote: > > Hi, group. For each database in a subset of my project's databases, I > would like to have a corresponding database that (almost) clones the > structure of the original database. The mirror databases will be used to > archive records that have been deleted from the original databases. > > For example, if I have db1 as the original database, with fields *id > *(automatically > generated)*, field1, field2, and field3*, db1_archive will have fields *id > *(automatically generated)*, original_id *(which will store the contents > of db1's id field)*, field1, field2, and field3.* > > The structure of an archive database should be updated automatically > whenever the structure of the original database is modified. Can anyone > recommend a good way to go about doing this? > > Also, is there a quick one/two-liner to transfer db (original) records to > db (archive) upon deletion from db (original), taking into account the > discrepancies in the *id *fields? Thanks. > -- --- 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/groups/opt_out.
