-->
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: casscading and triggers
PostPosted: Tue Jun 12, 2007 6:32 pm 
Newbie

Joined: Fri May 18, 2007 4:38 pm
Posts: 3
Location: phoenix
[b]Hibernate version:hibernate3.0

[b]Name and version of the database you are using: Oracle 9.2.0

we have a set of Tables say A, B C, D. A has a one to many relation with B and B has a one to many relation wtih C and C has a one to many relation with D. these relations are established using collection bag. Also B has the primary key of A as column, C has the primary key of B as column and so on. When we do an Insert into A, we are able to insert in to all tables(A,B,C &D ) with a single save like session.save(A). Hibernate internally generates the insert and update statements for the session.save(A) for each table.

we have triggers that get fired when we do an update on this tables. These triggers need to be fired only when the update to table is done manually.

we would like to distinguish between an update that we manually call like session.saveOrUpdate(A) and the internally generated update statement.

I would like to know if any users have faced this issue and how they have handled this issue.

thank you

Srini


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.