BTW, this bit from ZODB news _may_ be relevant:
- (3.6a4) ZODB 3.6 introduces a change to the basic behavior of Persistent
objects in a particular end case. Before ZODB 3.6, setting
``obj._p_changed`` to a true value when ``obj`` was a ghost was ignored:
``obj`` remained a ghost, and gettin
[Chris Withers]
> I'm trying to fix this bug:
> http://www.zope.org/Collectors/Zope/2062
>
> And I've narrowed it down to the following lines in History.py:
>
> ...
>
> If I comment out the base._p_changed=0 and base._p_deactivate() then
> history copy starts working again.
>
> ...
>
> Why was the
Hi All,
I'm trying to fix this bug:
http://www.zope.org/Collectors/Zope/2062
And I've narrowed it down to the following lines in History.py:
if serial != self._p_serial:
self.manage_beforeHistoryCopy()
state=self._p_jar.oldstate(self, serial)
print '1
