[ZODB-Dev] Recursion Error with ape and ZCatalog

[Klaus Woelfel]

Thanks for the quick anwer!

Shane Hathaway wrote:
>
> I'm pleased to hear Ape is being put to good use!
>
Yes, if when I find a way to solve the outstanding issues, ape is really the 
ideal storage for my zopeapplication mainly because it doesn't need to be 
packed (my application runs often on client computers, so the ever growing 
Data.fs isn't ideal). 
So I really apreciate your work on Ape!

>
> This doesn't happen when you index a smaller number of objects?
>

Yes, it works up to about 2800 objects with 22 indexes. With 12 indexes in the 
Catalog (and this time only one of them being a TextindexNG) it worked with 
5800 objects. 


> >
> > The same error occurs when adding a normal "old" textindex.
>
> Interesting.  The catalog is trying to store an acquisition wrapper,
> which is a bug in the catalog.  However, I thought I fixed this one a
> while back.  I wonder if I could make that error message display just a
> little more info.  (BTW that OID of '9' is nice, isn't it?  Ape OIDs are
> really simple now.)
>

What info would be needed to find the bug?

>
> You're doing nothing wrong.  ZCTextIndex apparently needs a minor fix
> somewhere.  (Standard ZODB hides this error.)

at what would I have to look when I would try to fix it?

>> Is the whole file loaded in memory when accessing one of the objects?
>
> Yes, by default Ape loads and stores database-like things as one big
> file.  We should look at serializing BTrees in a more scaleable manner.
>

is it the same in sql sorage? Are there all objects in the BTree stored in one 
big cell? What happens if only one object changes - is the whole file / cell 
rewritten?


Klaus

> Shane
>
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
>
> ZODB-Dev mailing list  -  ZODB-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zodb-dev