If one could operate under the assumption that most of the database fits
into memory, I would say the act of dealing with references that would
be left dangling is definitely better handled at the "business object"
layer. This would mean that in the "delete" method for each class, it
would know wh
While Elephant currently has a reasonable method for lazy handling of
broken dependencies (pointers from an object slot to an object that no
longer exists), it doesn't provide any reasonable method for computing
the set of broken dependancies when an object is dropped.
I'm finding for my cu
