[ZCM] [ZC] 922/ 2 Comment "Version feature is broken in Zope"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #922 Update (Comment) "Version feature is broken in Zope"
 Status Pending, Database/bug critical
To followup, visit:
  http://zope.org/Collectors/Zope/922

==============================================================
= Comment - Entry #2 by jeremy on Jan 17, 2004 4:33 pm

Can you confirm whether this bug exists with 2.6.3?  I vaguely recall fixing a bug in abortVersion that could have caused this behavior, but I can't find any evidence of it in the change logs.

________________________________________
= Request - Entry #1 by Anonymous User on May 22, 2003 11:04 am

Version feature is broken in Zope:

Working for some time with versions has caused two
times a corruption of Data.fs (Zope 2.5.1) in
our installation.

Test scenario description with a new (clean) Zope installation:
- Add Version to Root Folder: Id = "Test Version"
- Press Button: "Start Working in Test Version" in Test Version
- Add Line "Test" as 4th line to index.html
- Press Button "Quit Working in /Test Version" in Test Version
- call 'python <zope-dir>/lib/python/ZODB/fsrecover.py <zope-dir>/var/Data.fs /tmp/Data.fs'
Result:
Recovering /home/ndu/zope2.6/var/Data.fs into /tmp/Data.fs
. 1 . 2 . 3 . 4 . 5 . 6 . 7 . 8 . 9 .
ZODB.POSException.VersionLockError: ("'\\x00\\x00\\x00\\x00\\x00\\x00\\x00T'", '/Test Version')

0 . 1 . 2 . 3 . 4 . 5 . 6 . 7 . 8 . 9
319 bytes removed during recovery

I assume that this error leads after some time/changes
to a corruption of Data.fs

I get the above error for Zope 2.5.1 and Zope 2.6.2b1.
For Zope 2.5.1 the error can be resolved by packing the
Database. For Zope 2.6.2b1 the error persists.

==============================================================