Hi, Am Dienstag, den 25.04.2006, 23:50 -0400 schrieb Tres Seaver: > > Smells like a fix didn't get forward-ported somehow -- that looks like > the same error I helped Tim find and fix for Zope 2. > > CC'ing the ZODB list just in case anyone there has a better memory. > Here is the NEWS.txt entry for that fix: > > > DemoStorage > ----------- > > - (3.4a4) Appropriate implementations of the storage API's > ``registerDB()`` and ``new_oid()`` methods were added, delegating to > the base storage. This was needed to support wrapping a ZEO client > storage as a ``DemoStorage`` base storage, as some new Zope tests > want to do.
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. Christian -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Zope3-dev mailing list Zope3email@example.com Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com