[Zope] bobobase_modification_time problem

[Toby Dickenson]

On Friday 01 November 2002 12:26 pm, Andrei Cenja wrote:
> Hi,
>
> Due to a system clock error, our system's date was pushed forward a
> month; now the system date is back, ZopeTime() returns the right date,
> but any new object created still has the creation date a month into the
> future. Which is very bad, as most of the objects are time-dependent.
>
> Can this be changed, in other way than exporting everything and
> importing in a new Zope instance ? Zope-2.5.1, by the way.

bobobase_modification_time  comes from the transaction timestamp, and=20
FileStorage (or whatever storage you are using) is responsible for ensuri=
ng=20
that timestamps always go forwards. I think this will be a tricky one to=20
resolve.

The easy way out is to restore from a backup taken before this problem. I=
s=20
that possible?