Hi Chris,
Well, I certainly hope my response to Dave didn't seem like throwing
spears ;-) All I really wanted to say is that integrity problems are in all
realms. Actually, orders and other things should refer to a stock item, not
a catalog item's existence. In that way, the catalog item could be deleted
without harming other systems. Another alternative is just to be marked
'not available for catalog inclusion' with no actual deletions until all
dependencies are removed. And, of course, your thoughts are on the mark as
well.
Joe Sam
-----Original Message-----
From: Chris Raber <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, May 12, 1999 12:52 PM
Subject: Re: relational storage (was "Re: Granularity of EJBObjects")
>Gentlemen,
>
>Both points of view have merit.
>
>1. A good object model can use relationships as first class objects
>to manage the "can delete?" question. When product item is asked
>to delete itself, it can check if it is in any has-a relationships that
>would keep it from being deleted.
>
>2. A repository that can detect free floating objects with no references
>and automatically clean up is a good thing. In the case where #1 isn't
>done well, at least we won't end up with the "ghost reference" problem.
>
>Regards,
>
>-Chris, the peacemaker ;-)
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
