http://web2py.com/books/default/search/29?search=enable_record_versioning
On Wednesday, 26 December 2012 17:18:08 UTC-6, rh wrote: > > On Thu, 20 Dec 2012 11:21:21 -0800 (PST) > Cliff Kachinske <cjk...@gmail.com <javascript:>> wrote: > > > To enable archiving, I added enable_record_versioning(db) = True to > > my models files. > > I am curious about the versioning feature. > > How can you set a function call == True? > > I don't see any mention of enable_record_versioning in the book. > > From the book it says to do: > > form = SQLFORM(db.mytable, myrecord).process(onsuccess=auth.archive) > > or > > form = crud.update(db.mytable, myrecord, onaccept=auth.archive) > > > > > > > I encountered the problems described in the two bug reports I > > submitted today on Google code. > > > > At one point I thought it would help with isolating the problem if I > > turned off versioning, so I commented out the line enabling it. > > > > When I uncommented the line, I found tables with names like > > "products_archive_archive." These are archive tables for the archive > > tables. > > > > I suppose if I repeated the sequence I would have tables with names > > like "products_archive_archive_archive." > > > > On Thursday, December 20, 2012 10:05:25 AM UTC-5, Massimo Di Pierro > > wrote: > > > > > > I do not understand. Can you explain? > > > > > > On Thursday, 20 December 2012 08:11:42 UTC-6, Cliff Kachinske wrote: > > >> > > >> I just discovered that auth.enable_record_versioning will create > > >> archive tables for the archive tables if turned off and turned > > >> back on. > > >> > > >> Not acceptable. > > >> > > > > > > > -- > > > > > > > > > -- > > > --
