Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: pass (athena.apache.org: domain of kwsutter@gmail.com designates
 209.85.200.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=VN4b0iDlAzIUGHN2rRymdoVYXaXoqzQ+/yzs9JknHm3vAP8xeaNyr9CDU5kIy8F3ZK
         JSPgBXMea5FLobYY2uNvVJT1gdjkEK40iPVGyhLsQHJtv17i8Ej6IDQe+dey4T6lp18b
         0RAYJ/M8CJaD3j6KByjuOzyS5PBVDt6EpfQlI=
Message-ID: <89c0c52c0809190529h26344740q5367b3ad63916752@mail.gmail.com>
Date: Fri, 19 Sep 2008 07:29:31 -0500
From: "Kevin Sutter" <kwsutter@gmail.com>
To: users@openjpa.apache.org
Subject: Re: OpenJPA 1.2.0 Bug on FetchType.EAGER
In-Reply-To: <1221810595670-1100274.post@n2.nabble.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_29582_29632938.1221827371594"
References: <1221810595670-1100274.post@n2.nabble.com>

------=_Part_29582_29632938.1221827371594
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Egoosen2,
One new feature that went into 1.2.0 was the ability to cache some of the
generated sql on common queries.  Previous to this change, every query or
findBy operation required the same sql to be generated over and over again.
It may be possible that the caching is picking up the wrong sql for the
scenario that you describing.  As a quick test, could you try running with
this sql query cache turned off?  The property follows:

openjpa.jdbc.QuerySQLCache = false

If you could try this and let us know the results, it will help with
narrowing down the scope of the problem.

Thanks!
Kevin

On Fri, Sep 19, 2008 at 2:49 AM, egoosen <egoosen2@metropolitan.co.za>wrote:

>
> I'm experiencing a strange bug in 1.2.0, on an eager loaded one to many
> relationship.
> The first time I run the code, openJPA retrieves the parent entity and
> eager
> fetches the CORRECT child entities.
> The second time around, it fetches the parent entity and fetches the
> INCORRECT child entities (specifically, it fetches the child entities of
> the
> parent entity in the previous query).
>
> Here's the SQL to illustrate:
> First run:
> SELECT t0.AMDCTL_ID, t0.VRS_NBR, t0.AMDSEQ_CDE, t0.DPLORD_NBR, t0.FND_CDE,
> t0.RSL_DTE FROM EBSTATUS.TBL_AMDCTL t0 WHERE t0.FND_CDE = ?
> [params=(String) 0000001]
> SELECT t0.AMDCTL_ID, t1.AMDDES_ID, t1.VRS_NBR, t1.AMD_DES, t1.AMDCTL_ID,
> t1.EFC_DTE FROM EBSTATUS.TBL_AMDCTL t0 INNER JOIN EBSTATUS.TBL_AMDDES t1 ON
> t0.AMDCTL_ID = t1.AMDCTL_ID WHERE t0.FND_CDE = ? ORDER BY t0.AMDCTL_ID ASC
> [params=(String) 0000001]
>
> Second run:
> SELECT t0.AMDCTL_ID, t0.VRS_NBR, t0.AMDSEQ_CDE, t0.DPLORD_NBR, t0.FND_CDE,
> t0.RSL_DTE FROM EBSTATUS.TBL_AMDCTL t0 WHERE t0.FND_CDE = ?
> [params=(String) 0001001]
> SELECT t0.AMDCTL_ID, t1.AMDDES_ID, t1.VRS_NBR, t1.AMD_DES, t1.AMDCTL_ID,
> t1.EFC_DTE FROM EBSTATUS.TBL_AMDCTL t0 INNER JOIN EBSTATUS.TBL_AMDDES t1 ON
> t0.AMDCTL_ID = t1.AMDCTL_ID WHERE t0.FND_CDE = ? ORDER BY t0.AMDCTL_ID ASC
> [params=(String) 0000001]
>
> Somehow its caching the second query, even though I've turned off the
> DataCache and QueryCache.
>
> I've had to revert back to OpenJPA 1.1.0.
>
> Here's my mappings:
> TblAmdctl.java
> @OneToMany(mappedBy="tblAmdctl",fetch = FetchType.EAGER,cascade = {
> CascadeType.PERSIST,CascadeType.MERGE})
> private Collection<TblAmddes> tblAmddess = new ArrayList<TblAmddes>();
>
> TblAmddes.java
> @ManyToOne(fetch = FetchType.LAZY,cascade = {
> CascadeType.PERSIST,CascadeType.MERGE })
> @JoinColumns({@JoinColumn(name =
> "AMDCTL_ID",referencedColumnName="AMDCTL_ID")})
> @ForeignKey
> private TblAmdctl tblAmdctl;
>
> --
> View this message in context:
> http://n2.nabble.com/OpenJPA-1.2.0-Bug-on-FetchType.EAGER-tp1100274p1100274.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
>

------=_Part_29582_29632938.1221827371594--