I noticed two apparently minor errors with PM:
First:
2008-03-01 19:47:18 CET ERROR: prepared statement "TREE32FIRST" already exists
2008-03-01 19:47:18 CET ERROR: current transaction is aborted, commands
ignored until end
of transaction block
Second:
2008-03-01 20:42:35 CET ERROR: duplicate key violates unique constraint
"slots_qi_key"
2008-03-01 20:42:35 CET CONTEXT: SQL statement "INSERT INTO slots (qi, value)
VALUES (
$1 , $2 )"
PL/pgSQL function "ins_upd_slots" line 9 at SQL statement
Both of them might be the result of a race condition.
Also, PM's persistent slot reader will raise an UNBOUND-SLOT exception
instead of calling SLOT-UNBOUND. I believe the standard permits
not calling SLOT-UNBOUND when a slot is not bound, but it's
counter-intuitive anyway since that's the behaviour for STANDARD-CLASS
and there doesn't really seem to be any reason not to emulate this
behaviour.
Leslie
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
