Hello Gavin, Wednesday, July 21, 2004, 6:32:11 AM, you wrote:
> I've implemented support for ON DELETE CASCADE foreign key > definitions for parent/child associations (ie. for inverse > one-to-many). > You map this like: > <set name="children" inverse="true" cascade="all"> > <key name="PARENT_ID" on-delete="cascade"/> > <one-to-many class="Child"/> > </set> > So, when the Parent instance is deleted, Hibernate > does not need to perform n+1 deletes; instead, we > leave that to the database to take care of. > Any comments? Sounds like a nice and performant feature. By doing this we are now skipping/ignoring the LifeCycle stuff on these objects, correct ? And this is also a step in the direction of supporting efficient delete and update by query. Should we throw a warning (even exception) if one try to do this on a class that implements LifeCycle ? -- Best regards, Max Rydahl Andersen mailto:[EMAIL PROTECTED] www.hibernate.org ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
