[
https://issues.apache.org/jira/browse/OPENJPA-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750165#action_12750165
]
David Minor commented on OPENJPA-1280:
--------------------------------------
I didn't come up with a good fix for this, but as noted in the mailing list,
reverting the changes for OPENJPA-744 fixed this issue.
> OneToMany Bidirectional inverse relation not set when using data cache, fetch
> groups
> ------------------------------------------------------------------------------------
>
> Key: OPENJPA-1280
> URL: https://issues.apache.org/jira/browse/OPENJPA-1280
> Project: OpenJPA
> Issue Type: Bug
> Components: datacache
> Affects Versions: 1.2.0, 1.2.1
> Reporter: David Minor
> Attachments: test-eager-bidi-caching.patch
>
>
> If there is an instance of the other side of a OneToMany bidirectional
> relation in the data cache, and it was not fetched with the bidirectional
> relationship set (i.e., turned off in a fetch group), the inverse relation
> will remain null even when the "One" side is fetched normally.
> I believe this is what I was seeing here:
> http://n2.nabble.com/Problem-with-data-cache-inverse-relation-maybe-parallel-eager-results-td3400117.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
