openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1154) use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL
Date Mon, 06 Jul 2009 19:55:14 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kevin Sutter updated OPENJPA-1154:
----------------------------------

    Affects Version/s: 1.2.2
                       1.2.0
                       1.2.1
           Issue Type: Bug  (was: Improvement)

> 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: Bug
>          Components: sql
>    Affects Versions: 1.2.0, 1.2.1, 1.2.2, 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.


Mime
View raw message