It's interesting to know that this problem appears to show up on both branches. That narrows down the possibilities a bit.

Ian

On May 10, 2008, at 4:35 PM, Ryszard Szopa wrote:

On Sat, May 10, 2008 at 8:46 PM, Clinton Ebadi <[EMAIL PROTECTED] > wrote:
Ian Eslick <[EMAIL PROTECTED]> writes:
Also which version of the elephant tree?  This may be fixed on
unstable - there was quite a bit of general cleanup as I made the
schema changes.  Today, psets are just a wrapper around btrees -
anyone tried to reproduce this using straight btrees instead of psets?

This is with stable. I tried to use unstable for the program at first, but ran into weird issues with objects of different types ending up in
each others class indices.

I ran into the whole thing using unstable, which means that the
problem unfortunately hasn't disappeared. I also had the impression
that these are OIDs that have somehow leaked in a place they didn't
belong to.

Anyway, it makes me feel better knowing that this problem isn't local
for my application.

Cheers,

   -- Richard
--
http://szopa.tasak.gda.pl/
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

Reply via email to