I think the patch was scrubbed. Here it is again just in case.
Sat Jul 10 13:27:27 PDT 2010 redd...@gmail.com
* instance-table-bootstrapping-bug
Lazily load the indices-cache to avoid bootstrapping issues: If we do
not lazy-load the indices cache, it we attempt to initialize it before
Here is the patch. I identified a boostrapping issue:
(setf (instances-cache instance) (indices instance)) was being called
on an instance of BDB-INDEXED-BDB, forcing a deserialization of the
persistent INDICES slot. Unfortunately at this point in bootstrapping
the database, instance-table is no
When I try to open a controller of mine, I get this error:
The slot ELEPHANT::INSTANCE-TABLE is unbound in the object
#
It seems that this is caused by a bug with how the instance-table is
established in a new controller, since the stack trace indicates this
bug occurs when the INSTANCE-TABLE slo
