[ZODB-Dev] ZODB 3.9.3 history call causing problems for storages that still accept version parameters

[Christian Theune]

On 11/20/2009 01:07 AM, Chris Withers wrote:
> Jim Fulton wrote:
>> On Thu, Nov 19, 2009 at 6:07 PM, Chris Withers<chris at simplistix.co.uk>  wrote:
>>> Jim Fulton wrote:
>>>> So why not add a history method to ZEOStorage that passes size as a
>>>> keyword argument?
>>> I don't know what "ZEOStorage" is...

See StorageServer.py around line 80. As the docstring says it is a:
Proxy to underlying storage for a single remote client.

>> Then we shouldn't be having this conversation.
>
> I'm working off this traceback:
>
> Traceback (most recent call last):
>     File "ZODB3-3.9.3-py2.6-linux-i686.egg/ZEO/zrpc/connection.py", line
> 581, in handle_request
>       ret = meth(*args)
>     File "gocept.zeoraid-1.0b6-py2.6.egg/gocept/zeoraid/storage.py", line
> 219, in history
>       assert version is ''
>
> There is no ZEOStorage instance involved in this as far as I can tell.
> What am I missing?

Check the "setup_delegation" method: the history method is patched 
through directly so your traceback doesn't see the ZEOStorage anymore.

-- 
Christian Theune · ct at gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
Zope and Plone consulting and development