Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of michael.d.dick@gmail.com)
Date: Fri, 29 Apr 2011 12:02:29 -0700 (PDT)
From: Michael Dick <michael.d.dick@gmail.com>
To: users@openjpa.apache.org
Message-ID: <1304103749137-6317928.post@n2.nabble.com>
In-Reply-To: <1304097313912-6317642.post@n2.nabble.com>
References: <1304090274678-6317274.post@n2.nabble.com>
 <BANLkTik7=_Ou0r-ffxvDc+T0unZT0L8ydg@mail.gmail.com>
 <1304097313912-6317642.post@n2.nabble.com>
Subject: Re: Same JPQL, different results?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I can help with the different size of the result list. 

I think you're seeing  https://issues.apache.org/jira/browse/OPENJPA-894
OPENJPA-894 . The first time the results of a FETCH JOIN query are read from
the database OpenJPA only returns the unique rows. Subsequent FETCH JOIN
queries will return duplicates (as defined by the spec). There's also 
https://issues.apache.org/jira/browse/OPENJPA-1365 OPENJPA-1365 , which
complicates things.

I think the best workaround for these issues is to make use of OpenJPA's
FetchPlans to eagerly load a relationship. 

Something like this would work :


OpenJPAEntityManager em = OpenJPAPersistence.cast(entityManager);

FetchPlan plan = em.getFetchPlan();
plan.addField(Node.class, "children");

Query query = em.createQuery("SELECT n from Node n");

I'm not sure whether this will help with your detachment problem though, but
it's worth a try.

-mike--
View this message in context: http://openjpa.208410.n2.nabble.com/Same-JPQL-different-results-tp6317274p6317928.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.