[
https://issues.apache.org/jira/browse/OPENJPA-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031830#comment-13031830
]
Rick Curtis commented on OPENJPA-1989:
--------------------------------------
I fixed a bug where in JDBCStoreManager we rely on the return value from
FieldMetaData.isDefaultFetchGroupExplicit() to tell us when we can perform an
optimization. This optimization is to select the foreign id field(if they
exist) of a Lazy relationship. Due to my previous change, the explicit flag was
getting incorrectly changed when overriding mapping info via xml. Now XML vs
Annotations should behave the same in this scenario.
Committed revision 1101951 to trunk.
> *ToOne relationships specified as LAZY in xml aren't honored
> ------------------------------------------------------------
>
> Key: OPENJPA-1989
> URL: https://issues.apache.org/jira/browse/OPENJPA-1989
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 2.2.0
>
>
> While doing some testing I found that trying to override a [*]ToOne mapping
> as LAZY doesn't work. It is a simple change to the XML parser where when we
> find a ToOne element with a fetch specified, we need to explicitly set
> whether it is in the default fetch group.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
