Re: [web2py] Re: Beware auth.enable_record_versioning
On 3 January 2013 05:42, rh wrote: > I tried again in a fresh install and it failed again. So I created a new > app called "book" then unzip'd the contents of the git master into the > "book" app dir. And that seems to be working. > > I am also using this method, but I have observed that the book as displayed in the app is not the same as the online book. e.g. the section about the new auth.wiki does not display in the index or contents although a grep showed it is in the /sources subdirectories. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) --
[web2py] Re: Beware auth.enable_record_versioning
BTW... the book is now a public web2py app available on github. You can run and search the book locally without a connection. Massimo On Wednesday, 26 December 2012 19:55:39 UTC-6, rh wrote: > > On Wed, 26 Dec 2012 15:49:50 -0800 (PST) > Massimo Di Pierro > > wrote: > > > > http://web2py.com/books/default/search/29?search=enable_record_versioning > > Gracias, I may need to stop using the pdf version I have as that's not in > there. > I like to have pdfs in case I'm out of range. > > > > > On Wednesday, 26 December 2012 17:18:08 UTC-6, rh wrote: > > > > > > On Thu, 20 Dec 2012 11:21:21 -0800 (PST) > > > Cliff Kachinske > > > 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. > > > > >> > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > -- > > > > > > > > > -- > > > --
[web2py] Re: Beware auth.enable_record_versioning
The new edition is coming out by the end of january anyway. Perhaps sooner. Massimo On Wednesday, 26 December 2012 19:55:39 UTC-6, rh wrote: > > On Wed, 26 Dec 2012 15:49:50 -0800 (PST) > Massimo Di Pierro > > wrote: > > > > http://web2py.com/books/default/search/29?search=enable_record_versioning > > Gracias, I may need to stop using the pdf version I have as that's not in > there. > I like to have pdfs in case I'm out of range. > > > > > On Wednesday, 26 December 2012 17:18:08 UTC-6, rh wrote: > > > > > > On Thu, 20 Dec 2012 11:21:21 -0800 (PST) > > > Cliff Kachinske > > > 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. > > > > >> > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > -- > > > > > > > > > -- > > > --
[web2py] Re: Beware auth.enable_record_versioning
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 > 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. > > >> > > > > > > > -- > > > > > > > > > -- > > > --
[web2py] Re: Beware auth.enable_record_versioning
It appears to be fixed in trunk. I copied my entire app into a new directory. created a copy of the original db, data included. used appadmin to do fake migrates on all tables. commented out the enable_record_versioning in all model files. Turned off fake migrate. stopped and restarted the server (on my system rocket hangs after some kinds of model changes.) opened up appadmin on all affected applications - no errors. removed the comment to re-enable versioning again no problems with appadmin on affected apps. Since I copied the database into a new db, the tables with names like attachments_archive_archive were still present. It did not create any tables with names like attachments_archive_archive_archive. So I call it fixed. On Friday, December 21, 2012 1:20:03 AM UTC-5, Massimo Di Pierro wrote: > > This helped me a lot understand the problem. I believe I have a fix in > trunk. Can you please check if the problem is indeed solved? > > On Thursday, December 20, 2012 1:21:21 PM UTC-6, Cliff Kachinske wrote: >> >> To enable archiving, I added enable_record_versioning(db) = True to my >> models files. >> >> 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. >>> --
[web2py] Re: Beware auth.enable_record_versioning
Yes, but I don't think it will be today. On Friday, December 21, 2012 1:20:03 AM UTC-5, Massimo Di Pierro wrote: > > This helped me a lot understand the problem. I believe I have a fix in > trunk. Can you please check if the problem is indeed solved? > > On Thursday, December 20, 2012 1:21:21 PM UTC-6, Cliff Kachinske wrote: >> >> To enable archiving, I added enable_record_versioning(db) = True to my >> models files. >> >> 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. >>> --
[web2py] Re: Beware auth.enable_record_versioning
This helped me a lot understand the problem. I believe I have a fix in trunk. Can you please check if the problem is indeed solved? On Thursday, December 20, 2012 1:21:21 PM UTC-6, Cliff Kachinske wrote: > > To enable archiving, I added enable_record_versioning(db) = True to my > models files. > > 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. >>> >> --
[web2py] Re: Beware auth.enable_record_versioning
To enable archiving, I added enable_record_versioning(db) = True to my models files. 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. >> > --
[web2py] Re: Beware auth.enable_record_versioning
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. > --
