-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Hibernate's built-in cascade vs. database's cascade options
PostPosted: Sun Sep 04, 2011 7:01 am 
Newbie

Joined: Sat Sep 03, 2011 10:16 am
Posts: 10
Hi,

Hibernate has built-in "cascade" options for one-to-one/one-to-many relations, but how do these related to the database's own CASCADE actions?

For example, if I have already defined a foreign key in a table with ON DELETE CASCADE ON UPDATE CASCADE, do I really need to define cascade="delete" in Hibernate as well? And what would happen if I did tell Hibernate to cascade deletes, and the database already deleted the children?

And will Hibernate create INSERT/UPDATE statements for child collections when I use session.save(Parent)?


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.