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
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
Cool (and not so cool). This indicates that we have a potential problem
with our sql query caching support. Do you have access to our JIRA system?
If so, please go ahead and open a JIRA Issue for this problem. If not, I
(or another developer) can open one for you. We need to figure this one
Hi,
I can reproduce this problem. Please open a JIRA for this problem. Thanks!
-Fay
--- On Fri, 9/19/08, egoosen [EMAIL PROTECTED] wrote:
From: egoosen [EMAIL PROTECTED]
Subject: OpenJPA 1.2.0 Bug on FetchType.EAGER
To: users@openjpa.apache.org
Date: Friday, September 19, 2008, 12:49
Sorry, I spoke too soon. My test case actually runs fine. The following
listings are my TblAmdCtl.java, TblAmdDes.java and TestQuerySQLCache. Could you
attach your test case to reproduce this problem in the JIRA? Thanks!
(1) TblAmdCtl.java
@Entity
public class TblAmdctl {
