You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2014/02/11 21:25:37 UTC
svn commit: r1567358 -
/isis/site/trunk/content/components/objectstores/jdo/managed-1-to-m-relationships.md
Author: danhaywood
Date: Tue Feb 11 20:25:37 2014
New Revision: 1567358
URL: http://svn.apache.org/r1567358
Log:
fixing links
Modified:
isis/site/trunk/content/components/objectstores/jdo/managed-1-to-m-relationships.md
Modified: isis/site/trunk/content/components/objectstores/jdo/managed-1-to-m-relationships.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/components/objectstores/jdo/managed-1-to-m-relationships.md?rev=1567358&r1=1567357&r2=1567358&view=diff
==============================================================================
--- isis/site/trunk/content/components/objectstores/jdo/managed-1-to-m-relationships.md (original)
+++ isis/site/trunk/content/components/objectstores/jdo/managed-1-to-m-relationships.md Tue Feb 11 20:25:37 2014
@@ -2,7 +2,7 @@ Title: Managed 1:m bidirectional relatio
When an object is added to a 1:m bidirectional relationship, the child object must refer to the parent and the child must be added to the parent's children collection.
-In general, *Isis* recommends that the mutual registration pattern is ensure that both the parent and child are updated correctly; the framework supports the `modifyXxx()` and `clearXxx()` methods to accomplish this, and this [how-to](../../../applib-guide/how-tos/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html) describes the boilerplate necessary.
+In general, *Isis* recommends that the mutual registration pattern is ensure that both the parent and child are updated correctly; the framework supports the `modifyXxx()` and `clearXxx()` methods to accomplish this, and this [how-to](../../../more-advanced-topics/how-to-04-060-How-to-set-up-and-maintain-bidirectional-relationships.html) describes the boilerplate necessary.
However, in a relational database, these two operations in the domain object model correspond simply to updating the foreign key of the child table to reference the parent's primary key.