Hi!
Dan OConnor wrote:
> <spec>Detaching a dependent object that has already been
> entered into the data source from all of the container managed
> relationships in which it participates does not cause the persistent
> representation of the dependent object to be removed. The
> dependent object will continue to exist in the data store as a
> detached dependent object. It will not be reachable by navigation
> but can be accessed by an EJB QL query.</spec>
>
> How would this work for the typical one-to-one or one-to-many
> containment relationship, where the persistent relationship
> information is part of the object's identity?
Good question. I assume your question relates to how to model the
relationship in database tables, i.e. if one uses a separate
relationship table or not. My intuition says that it is not a problem
really. You can still use table columns for such relationships.
Do you have a particular case which you think will be problematic? Can
you outline what the problems would be?
regards,
Rickard
