[
https://issues.apache.org/jira/browse/JDO-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526007
]
Craig Russell commented on JDO-521:
-----------------------------------
> The spec says "In particular, making a change to one side of the relationship
> does not imply any runtime behavior by the JDO implementation to change the
> other side of the relationship in memory prior to flush" but that doesn't by
> my reading prohibit updating the in memory model, and so for any
> implementation that does update in-memory on each change these "negative"
> tests will fail since they don't allow for it. Or is it that there is some
> requirement to prohibit this ? An implementation *can* flush changes to the
> datastore without user-called flush() or commit() (unless using optimistic
> txns).
>From the spec, "Conflicting changes include:
• adding a related instance with a single-valued mapped-by relationship field
to more than
one one-to-many collection relationship
• setting both sides of a one-to-one relationship such that they do not refer
to each other"
If you update both sides immediately, when would there ever be a conflicting
change?
> 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.
