[
https://issues.apache.org/jira/browse/OPENJPA-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262728#comment-13262728
]
Jeremy Bauer commented on OPENJPA-2141:
---------------------------------------
Mark - given that none of your fields are marked lazy, I'd guess what you've
described is a separate issue. It looks like our logic to determine whether a
lob can be fetched inline may need to be reviewed for certain queries. Each DB
vendor also has various levels of support for inlining so what you see could be
DB specific as well. Unless the fields in the embeddable are tagged as lazy,
I'm not sure why we'd need to fetch them separately. That sounds like a bug.
Any chance you can provide a testcase? I could at least verify what I've added
for this JIRA hasn't broken anything.
> Lazy fetch of embedded attributes does not work properly
> --------------------------------------------------------
>
> Key: OPENJPA-2141
> URL: https://issues.apache.org/jira/browse/OPENJPA-2141
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.3.0, 2.2.1
> Reporter: Jeremy Bauer
> Assignee: Jeremy Bauer
>
> OpenJPA's @Persistent annotation and configuration via OpenJPA's xml
> extensions provide a mechanism to mark embedded fields lazy. When trying to
> use this facility I found a couple bugs.
> Bug 1: The xml extension does not process the fetch attribute, so the field
> is never marked lazy.
> Bug 2: If marked lazy via the annotation or xml (with a fix) the lazy field
> does not get loaded along with the entity (as expected), but then will not
> load when accessed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
