openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "B.J. Reed (JIRA)" <j...@apache.org>
Subject [jira] Created: (OPENJPA-1154) use of getFetchPlan().setMaxDepth(x) puts DISTINCT in the SQL
Date Wed, 01 Jul 2009 19:41:47 GMT
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


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