On Thu, 22 Mar 2007 17:46:31 +0100 Jens Vagelpohl <jens@dataflake.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22 Mar 2007, at 17:11, flem wrote:
Through a zwiki a spammer proxied some information though a zope server using zwiki's comments (be aware!). The spammer had dated his ip-packets 11/12-2007. And all my changes got the same date! So, I couldn't shrink all the undo actions though the database shrinker (later I found out that should just use -300). To get rid of 10 GB of undo history, I changed the computers time to 12/12-2007 and then undoed and gave the computer the right time again. Fine!
But, now, not only have all my changes the date 12/12-2007 in the undo history, every object I have changed gets this date as well! Apparently, zope won't accept to go backward in time.
How do I reset the zope's time?
Undo is transactional, meaning an undo is actually a new transaction instead of removing an old transaction. What you are trying to do is not possible, unless you physically truncate the database.
I am not absolutely sure I understand you. I succeeded in undoing. My problem is that zope keeps on with the date 12/12-07. The zodb does not seem to accept a timestamp that is earlier than the last ... Flemming