[
https://issues.apache.org/jira/browse/OPENJPA-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262681#comment-13262681
]
Mark Struberg commented on OPENJPA-2141:
----------------------------------------
Actually I found a bug which could be related to this.
I have an Entity (Course) with a simple @Embedded field and a @Lob. I do not
use any LAZY attribution on them!
If I do a normal em.find, the entity will be loaded as a whole (all the fields,
including the embedded and the lob will be fetched immediately).
Sidenote: the Lecturer referred in the select is defined as
@OneToMany(mappedBy = "course",
cascade = {CascadeType.PERSIST, CascadeType.REMOVE,
CascadeType.MERGE},
orphanRemoval = true, fetch = FetchType.EAGER)
@OrderColumn(name = "POSITION")
private List<Lecturer> lecturers;
The following selects DO work
* "select c from Course c join c.lecturers l "
* "select distinct c from Course c"
The following selects create tons of subqueries! 1 separate sub-query for each
@Embedded field, and also for each @Lob
* "select distinct c from Course c join c.lecturers l "
* "select distinct c from Lecturer l join l.course c"
* "select c from Lecturer l join l.course c"
Should I create a separate issue or do you think it's related?
> 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
