> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jay Walters
> I'm having a hard time visualizing a case where you want the behaviour which
> the spec talks about in terms of detachment, no cascade delete and keep
> unnavigable rows around.
Several possible scenarios:
- They might be unnavigable only for a limited period of time, waiting to be
incorporated in different relationships later on.
- Non-EJB processes might want to use them.
- They can still be found through EJB-QL, so they're not worthless.
In all cases, and given the typical profile of a machine hosting your DB,
keeping a row even if it's not used for a while is probably preferable to
deleting it and inserting it again later.
On a separate issue, cascade-delete is a very powerful (and thus dangerous)
weapon. It can have disastrous effects if you have misconfigured your
relations. Not mentioning the impact on performance when your cascading delete
starts hitting 1-1 relationships. It used to be the default, we convinced Sun
it shouldn't be, we're certainly glad they agreed :-)
--
Cedric
