Has any progress been made on this SBCL / pset issue? I would like to
help resolve this, as I am suffering from this problem too. If someone
could describe the specifics of the problem between SBCL and elephant, I
will take a closer look.
Thanks.
Kevin
On Tue Jun 12 10:37:09 EDT 2007, Ian
Well, that was a silly bug. I just checked in a patch. Please let
me know if it works for you now.
Ian
On Jun 8, 2007, at 8:49 PM, Brian Seitz wrote:
Hey,
I've been experimenting with Elephant, and it's been really great
so far.
But I've had one strange issue. When I make a pset, its
Ok, please ignore my prior e-mails and fixes. There is a definite
problem deserializing psets that only shows up in SBCL.
I'll get back to y'all.
Ian
On Jun 12, 2007, at 10:20 AM, Ian Eslick wrote:
Actually, I now remember that I had intended to implement psets as
ordinary classes to avoi
Actually, I now remember that I had intended to implement psets as
ordinary classes to avoid allocating two persistent objects as the
patch now does. The actual bug was not remembering the oid of the
btree, but the new fix is probably cleaner anyway.
Ian
On Jun 12, 2007, at 10:18 AM, Ian
Hey,
I've been experimenting with Elephant, and it's been really great so far.
But I've had one strange issue. When I make a pset, its btree slot
always becomes unbound after I've closed and re-opened the store.
I've tried this with bdb, sqlite, and postgresql, all with the same
result. Using
