[
https://issues.apache.org/jira/browse/JDO-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526033
]
Craig Russell commented on JDO-521:
-----------------------------------
The reason that conflicting changes aren't portable is that depending on the
order of operations, different results would obtain. For example, in the
negative test scenario,
+ pm.makePersistent(medInsNew);
+ medIns2.setEmployee(emp1);
+ emp1.setMedicalInsurance(medInsNew);
+ doFlush(testMethod);
If you reverse the order of operations,
+ pm.makePersistent(medInsNew);
+ emp1.setMedicalInsurance(medInsNew);
+ medIns2.setEmployee(emp1);
+ doFlush(testMethod);
If you allow these two sequences to be valid and result in different changes to
the datastore, I think there is a problem.
> Create tests for relationship mapping (spec section 15.3)
> ---------------------------------------------------------
>
> Key: JDO-521
> URL: https://issues.apache.org/jira/browse/JDO-521
> Project: JDO
> Issue Type: Test
> Components: tck2
> Affects Versions: JDO 2 maintenance release 1
> Reporter: Michelle Caisse
> Assignee: Michelle Caisse
> Attachments: JDO-521.patch
>
>
> We need a set of tests to test that an implementation syncs both sides of a
> relationship on flush().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
