What happens when a deletion occurs? The simplistic route would be to delete everything. But that is unlikely to be normal. And the logic to determine that it can stop before deleting everything is certainly going to be more complicated than just a depth level.
And how the deletion occurs would be problematic. The container would have to do an update (null a key in the parent) before deleting the child. Otherwise constraints might be violated. That is certainly much more work than it has to do now. The container can't rely on the database for this because it must update the entity that no longer has the relationship. How would you express such restrictions in the descriptor? It certainly can't be done in a pseudo SQL syntax. So that implies some other tags. But what would the format of such a tag be? Juan Alvarez wrote: > Suppose yo have the following tables: > > tbl_x > ----- > id_a > id_b > > tbl_y > ----- > id_c > > And the following relationships between this tables: > > tbl_x (id_a) MANY <----------> ONE tbl_y (id_c) > tbl_x (id_b) MANY <----------> ONE tbl_y (id_c) > =========================================================================== 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".
