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
The traces that you saw comes from the new catalog (the btree one).
----- Original Message -----
From: "Chris Withers" <[EMAIL PROTECTED]>
To: "Giovanni Maruzzelli" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "Chris McDonough"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, June 28, 2001 6:27 PM
Subject: Re: [Zope-dev] Re: Zcatalog bloat problem (berkeleydb is a
> 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
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -