Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of awhite@bea.com designates
 82.195.180.133 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <4100235.1176416235298.JavaMail.jira@brutus>
References: <4100235.1176416235298.JavaMail.jira@brutus>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6E8458EE-DA56-4365-B425-03D9147C1D37@bea.com>
Content-Transfer-Encoding: 7bit
From: Abe White <awhite@bea.com>
Subject: Re: [jira] Commented: (OPENJPA-134) Extra unneeded SQL joins for
 OneToMany relationship with fetch type EAGER
Date: Fri, 13 Apr 2007 09:32:09 -0500
To: open-jpa-dev@incubator.apache.org

> I did notice that my lazy scenarios are almost 50% slower now, but  
> looking at the sql dumps it appears that we were fetching eagerly  
> even in those scenarios and this (or another JIRA?) seems to have  
> fixed that functional error.  Does that seem like something your  
> changes would resolve?  Did you run into anything that would cause  
> an eager fetch even when lazy was specified?

I had no intention of "fixing" any lazy loading behavior.  The fact  
that you're seeing different behavior makes me nervous.  Can you post  
details on the entities and the test case so we can determine for  
sure whether the new or old behavior is correct?

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.