[Zope] bobobase_modification_time problem

[Andrei Cenja]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Toby Dickenson wrote:<br>
<blockquote type="cite"
 cite="mid200211011237.37766.tdickenson@geminidataloggers.com">
  <pre wrap="">On Friday 01 November 2002 12:26 pm, Andrei Cenja wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
bobobase_modification_time  comes from the transaction timestamp, and 
FileStorage (or whatever storage you are using) is responsible for ensuring 
that timestamps always go forwards. I think this will be a tricky one to 
resolve.

The easy way out is to restore from a backup taken before this problem. Is 
that possible?</pre>
</blockquote>
Ouch :-)<br>
For various reasons, no backup is yet available. <br>
<br>
</body>
</html>