(I fixed that oids-only problem. It's a tweak I'm adding to improve join efficiency in the new query planner. Sorry that crept into the main code base).
I highly recommend you switch to the new repository, elephant-1.0. We should be able to figure out any problems you have shortly. Regards, Ian On Jan 3, 2009, at 11:50 AM, Hugo Duncan wrote: > > Changing to use elephant stable gets rid of the problem. Not sure > why I > was using unstable - I know I switched back and forth several times > when > trying to get something to work when I started working with elephant. > Which of stable/unstable do you recommend using? > > BTW, to use unstable I had remove the OIDS-ONLY argument from > PERSISTENT-SLOT-READER in pm-controller.lisp. > >> also it might make sense to instrument function get-cached-instance a >> bit to know whether crippled pm-btree is recreated or just retrieved >> from cache. something like: > > The code in unstable is different (and has a redundant AWHEN), but > instrumenting it shows that when the problem occurs, the crippled pm- > btree > is being recreated (not in cache). > > If there are any other tests you would like me to run, I would be > happy to > do so. In the meantime, I'll just use stable. > > Many thanks for your help, and apologies for not having tried stable > before. > > Hugo > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > _______________________________________________ > 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
