we have a ZODB with a future timestamp, somewhere around 2030, after a mistake
while setting the system time. After setting back system time the zope
modification time of all new objects stay at the latest time.
System: Zope 2.9.7 (ZODB 3.6.2?)/Plone 2.5x
I reproduced this problem on a local server, to figure out how to fix it.
While searching the net, i found this discussions
Following this "instructions" i copied the data.fs with the patched version of
copyTransactionsFrom with a little script like this:
old_fs = FileStorage('var/filestorage/Data.fs', read_only=True)
iter = old_fs.iterator()
new_fs = FileStorage('var/filestorage/newfs.fs', create=True)
And at first it seems to work, but only for objects that haven't changed during
the wrong sytemdate time.
This error happens while modifing content in plone and zope
and this while adding content in plone and zope
Maybe i've done something wrong while creating the new data.fs. Or there is
another solution to fix this problem.
I hope you can give me hint/tip/instruction or anything else to solve it.
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org