[Zope3-dev] Re: ClientStorage vs DemoStorage broken in Zope 3.2?

[Christian Theune]

Hi again,

Am Mittwoch, den 26.04.2006, 08:05 +0200 schrieb Christian Theune:
> I remembered there was a fix like that. Unfortunately that fix was
> ported to the 3.6 branch actually. I'm poking around myself a bit more. 
> 
> What I found right now is that BaseStorage accesses an attribute "_oid"
> on the Storage given as a Base to find the highest oid currently used.
> This is used for the new_oid implementation as a comment right before it
> tells.
> 
> I'll keep looking and try to find a fix.

Now. I found a way to fix it, by letting BaseStory in its __init__
method only do:

 self._oid = base._oid

by changin this to read:

 if hasattr(base, '_oid'):
       self._oid = base._oid

Obviously this code is the same in the 3.4 branch, but doesn't break
over there, so I'm pretty sure I'm only fixing symptoms, not the real
cause.

Christian

-- 
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20060426/1e56f817/attachment.bin