Comments on: How To: NHibernate Parent/Child Relationships http://dustyreagan.com/how-to-nhibernate-parentchild/ On Technology & Entrepreneurship Thu, 29 Jul 2010 23:29:01 -0700 hourly 1 http://wordpress.org/?v=3.0 By: garth engdahl http://dustyreagan.com/how-to-nhibernate-parentchild/comment-page-1/#comment-82 garth engdahl Fri, 01 May 2009 17:05:16 +0000 http://dev.dustyreagan.com/?p=40#comment-82 hmm. my example of the mapping appears to have been eaten in the previous post. here it is again... <!-- Many-to-One Foreign Key Association: Organization --> <!-- Save Foreign Key reference, but don't cascade update/deletes --> hmm. my example of the mapping appears to have been eaten in the previous post. here it is again…

<!– Many-to-One Foreign Key Association: Organization –>
<!– Save Foreign Key reference, but don’t cascade update/deletes –>

]]> By: garth engdahl http://dustyreagan.com/how-to-nhibernate-parentchild/comment-page-1/#comment-81 garth engdahl Fri, 01 May 2009 17:03:23 +0000 http://dev.dustyreagan.com/?p=40#comment-81 a related question. we have a parent/child relationship set up between class A and class B. class B has a back-pointer to it's parent - parentA. the mapping for the property in Class B looks like this (sorry for the formatting)... As can see, cascade is set to "none". So i assumed that when we saved an instance of the child class B nothing would happen to the parent object A. Ah, but it turns out that if you update the instance of class A which is hanging off of class B and the update class B the change to A is persisted to the database and the version number on class A is incremented. Sort of exactly the same behaviour i would have expected if cascase="true". Any thoughts on why this is happening, anyone? thanks, Garth Engdahl a related question. we have a parent/child relationship set up between class A and class B.
class B has a back-pointer to it’s parent – parentA. the mapping for the property in Class B looks like this (sorry for the formatting)…

As can see, cascade is set to “none”. So i assumed that when we saved an instance of the child class B nothing would happen to the parent object A. Ah, but it turns out that if you update the instance of class A which is hanging off of class B and the update class B the change to A is persisted to the database and the version number on class A is incremented. Sort of exactly the same behaviour i would have expected if cascase=”true”. Any thoughts on why this is happening, anyone?
thanks,
Garth Engdahl

]]>