[
https://issues.apache.org/jira/browse/OPENJPA-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
B.J. Reed updated OPENJPA-1154:
-------------------------------
Attachment: TestFetchPlanDepth.java
> use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL
> -------------------------------------------------------------
>
> Key: OPENJPA-1154
> URL: https://issues.apache.org/jira/browse/OPENJPA-1154
> Project: OpenJPA
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.0.0
> Environment: DB2 and Windows
> Reporter: B.J. Reed
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: TestFetchPlanDepth.java
>
>
> Use of q.getFetchPlan().setMaxFetchDepth(x); // x is any depth
> will always add DISTINCT to the generated SQL. Seems like the DISTINCT
> shouldn't be added.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
