[
https://issues.apache.org/jira/browse/OPENJPA-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-1365:
----------------------------------
Attachment: OPENJPA-1365-1.0.x-patch.txt
Attaching patch for 1.0.x. It requires the changes for OPENJPA-894 however.
both issues use the same testcase, and those are duplicated in the patch (I'll
fix this when OPENJPA-894 is committed).
> DISTINCT keyword has no effect with JOIN FETCH queries
> ------------------------------------------------------
>
> Key: OPENJPA-1365
> URL: https://issues.apache.org/jira/browse/OPENJPA-1365
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa, query
> Affects Versions: 1.0.4, 1.2.2, 1.3.0, 2.0.0-M4
> Reporter: Michael Dick
> Assignee: Michael Dick
> Attachments: OPENJPA-1365-1.0.x-patch.txt
>
>
> This issue occurs if the proposed fix for OPENJPA-894 is in place. Without
> that fix there results of a JOIN FETCH are always distinct when obtained from
> the database or non-distinct when returned from the persistence context's L1
> cache.
> I started a discussion on this topic on the dev mailing list. The entire
> thread can be seen on Nabble here :
> http://n2.nabble.com/How-should-we-handle-the-JPQL-DISTINCT-keyword-td3908400.html#a3908400
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
