The answer to mostly of your questions is yes. Automated packing of the database is pretty easy with wget and cron. Capture the URL that gets sent when you click on pack, then put that in a wget cron job with the appropriate authentication. This is left as an exercise for the reader (although someone will probably give you a crib sheet before you even read this message). Undo can be removed by changing ZODB to use a different backing store. See, for example: http://www.zope.org/Products/OracleStorage http://www.zope.org/Members/tsarna/BerkeleyStorage There might be others. As for learning about transactions: I'm not sure. Try the developer docs or look for ZODB docs.
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Joakim Nicander Sent: Thursday, November 07, 2002 5:20 AM To: zope@zope.org Subject: [Zope] Limit transaction undo
Hello!
We are using Zope for several customers where we built an interface to maintain their own websites. Working very well, but the ZODB will grow because of all saved transactions.
We don't need the saved transactions since we do all the production on another server.
Today we manually pack the ZODB regularly, but it would be nice to either stop or limit this feature. I have searched but haven't found any hint on how to do this. Is it possible?
If not, is there a way to automatically pack the ZODB regularly?
Another odd thing is that I see transactions saved when a dtml-method has been viewed. The method doesn't contain anything that do any changes to the ZODB. But I need to do some more testing and learn how Zope handles transactions before be absolutely sure.
Where can read more about how/what Zope saves transactions? The handbook didn't go in to any details.
Joakim Nicander