Brian Hooper wrote:
Hi everyone,
I have a Z ODB (version 2, running with 1.10.3) that got corrupted when something went wrong with my system clock, causing the Z ODB to get filled with a lot of time stamps which are stuck in the future.
Is there an easy way to fix this? Do I need to go through all the records in the database and set the time backwards, or something like that? If someone has an easy way to deal with this, please let me know!
Look at the fixbbbts.py module in the utilities directory of a Zope 2 distribution. It is intended to fix this. Note that ZODB 3 is more forgiving of time stamps in the future. (It whines in the log, but otherwise ignores them.) Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.