[elephant-ticket] Re: #3: Referential Integrity

[elephant]

#3: Referential Integrity
---------------------------+------------------------------------------------
  Reporter:  ieslick       |       Owner:  ieslick      
      Type:  defect        |      Status:  new          
  Priority:  blocker       |   Milestone:  Release 0.9.1
 Component:  metaprotocol  |     Version:               
Resolution:                |    Keywords:               
---------------------------+------------------------------------------------
Comment (by ieslick):

 If we use the oid table to determine class as well as validity, then we
 can have a one or more parameter-selectable system policy that dictates
 what to do if we try to deserialize a deleted object:
 - return nil
 - return a special object
 - return a fresh version of the object
 - call a handler (what would it be defined on, a class?)
 - assert a user continuable and restartable error

-- 
Ticket URL: <http://trac.common-lisp.net/elephant/ticket/3>
elephant <http://common-lisp.net/project/elephant>
elephant