Community
Participate
Working Groups
Given the following scenario: @Entity class A { B originalB; B currentB; .. } @Entity class B { .. } in the case of A.currentB == A.originalB Eclipseling2.1.1 executes following selects for a find(A.class): select from a... select from b... Eclipselink2.4 executes one more select: select from a... select from b... select from b... Eclipseling2.1.1 seems to realize, that originalB==currentB and that it only has to query for one B, which can be assigned to both originalB and currentB. Eclipselink2.4 always seems to execute a distinct query for each relationship.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
I cannot reproduce this. What is the mapping for B? Please include a test the recreates the issue.
Created attachment 226700 [details] test case Added a test case. It's a bit more complicated. The first relationship to B is join-fetched. The second is contained in an embeddable C. run maven clean install run startstandalone.sh .hg/patches contains a patch to switch the test case from 2.4 back to 2.1.1.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink