The Zope version we use contains the new btree catalog by default. So, when we recreated the catalog from scratch, it was created as a btree catalog. The traces that you saw comes from the new catalog (the btree one). -giovanni ----- Original Message ----- From: "Chris Withers" <chrisw@nipltd.com> To: "Giovanni Maruzzelli" <maruzz@open4.it> Cc: <tdickenson@geminidataloggers.com>; "Chris McDonough" <chrism@digicool.com>; <a.deuring@satzbau-gmbh.de>; <zope-dev@zope.org>; <erik@thingamy.net>; <barry@digicool.com>; <tsarna@endicor.com> Sent: Thursday, June 28, 2001 6:27 PM Subject: Re: [Zope-dev] Re: Zcatalog bloat problem (berkeleydb is a solution?)
Giovanni Maruzzelli wrote:
The catalog is a pristine 2.3.3b1 catalog.
I'm sure that'll need upgrading then...
We have recreated the catalog from scratch because we tried manage_convertBTrees , but it don't work for us, it return with an error (and the same happens with 2.3.3 final):
Error Type: TypeError Error Value: second argument must be a class
Weird... from your earlier posting it looked like you _had_ successfully upgraded and updated (BTrees.IOBTree in your traceback rather than IOBTree.IOBTree)
cheers,
Chris