[
https://issues.apache.org/jira/browse/OPENJPA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Sutter reassigned OPENJPA-135:
------------------------------------
Assignee: Catalina Wei
Now that Catalina is a full-fledged committer, maybe she can help determine the
fate of this Issue... :-)
This is quite an old Issue. We should determine whether this problem even
exists any longer. And, if so, can we get it resolved before the 1.0.0
deadline or should it be moved out? I'm hoping Catalina can help figure out
the right course of action.
Thanks,
Kevin
> join fetch not returning duplicate references which not conforming to ejb3.0
> spec
> ---------------------------------------------------------------------------------
>
> Key: OPENJPA-135
> URL: https://issues.apache.org/jira/browse/OPENJPA-135
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Reporter: Catalina Wei
> Assignee: Catalina Wei
> Fix For: 1.0.0
>
>
> In the description in EJB 3.0 JPA spec, section 4.4.5.3, the following query
> example
> SELECT d
> FROM Department d LEFT JOIN FETCH d.employees
> WHERE d.deptno = 1
> The spec says this query returns 5 references to the department 1 entity if
> department 1 has 5 employees.
> The same query running with openjpa code, it returns only 1 reference to
> department 1 entity.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
