Thanks. If there is a disconnect between this and the book we can fix it in the next version. Please open a ticket about this.
On Feb 21, 5:15 pm, simon <[email protected]> wrote: > 4th edition current online version: > > http://web2py.com/books/default/chapter/29/7?search=archive > > Also there is no mention of archive_current. I found that in a post on > this forum > > http://groups.google.com/group/web2py/browse_thread/thread/f4e37fe918... > > On Feb 21, 10:30 pm, Massimo Di Pierro <[email protected]> > wrote: > > > > > > > > > There was an accidental change of behavior. You are the first to > > notice that. You have the option to do one or the other. The issue is > > what should be default of archive_current. > > > what book edition are you looking at? > > > On Feb 21, 3:14 pm, simon <[email protected]> wrote: > > > > The book says that auth.archive "stores a copy of the record (as it > > > was before the update)". However with SQLFORM it appears to store a > > > copy of the record after the update unless you do workaround (from > > > Anthony in previous post): > > > > if form.process(...onsuccess=lambda archive: auth.archive(form, > > > archive_current=False)) > > > > Seems to me the book version is more intuitive.
