With the latest Git revision on SBCL 1.0.51, when trying to migrate
objects that have a derived slot, elephant tries to call setf
slot-value-using-class on the derived slot, resulting in an error :
"Cannot write computed (derived) slot... for read/index retrieval
only".
It seems to me that copy-pe
hi
i've promised to fix some bugs in db-postmodern and make it ready for 1.0
"soon", but unfortunately those issues were much more serious than i thought
(i found some more bugs), and that required considerable changes. but
finally it seems to be done, now i'm doing tests and making patches.
m
I should have said ":weak allows map-class over any class instances
not explicitly deleted or GC'd"
Ian
On Mar 22, 2008, at 11:47 AM, Ian Eslick wrote:
Good suggestion!
I implemented this via the original :index class option which is 't'
by default but can also be 'nil' (asserts an error o
Good suggestion!
I implemented this via the original :index class option which is 't'
by default but can also be 'nil' (asserts an error on get-instances-by-
class/map-class) and ':weak' which inhibits copying class elements
that aren't reachable from root during migration, but allows map-cl
On Sat, Mar 22, 2008 at 5:11 AM, Ian Eslick <[EMAIL PROTECTED]> wrote:
> In the past, we've been able to reclaim instances that were not
> reachable from the root or in an indexed object. However, with the
> new schema model, all persistent objects are reachable implicitly by
> being in the store
In the past, we've been able to reclaim instances that were not
reachable from the root or in an indexed object. However, with the
new schema model, all persistent objects are reachable implicitly by
being in the store's oid->class table (i.e. a get-instances-by-class
now works for any per
