From noreply at atlassian.com Tue Sep 5 02:52:24 2006 Content-Type: multipart/mixed; boundary="===============7263489449695837152==" MIME-Version: 1.0 From: Christian Bauer (JIRA) To: hibernate-issues at lists.jboss.org Subject: [hibernate-issues] [Hibernate-JIRA] Commented: (ANN-430) @ManyToOne results in default outer join eager fetch, should be lazy Date: Tue, 05 Sep 2006 01:52:24 -0500 Message-ID: <78278684.1157439144444.JavaMail.j2ee@atlassian01.managed.contegix.com> In-Reply-To: 89254774.1157128104447.JavaMail.j2ee@atlassian01.managed.contegix.com --===============7263489449695837152== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-430?pag= e=3Dcomments#action_24303 ] = Christian Bauer commented on ANN-430: ------------------------------------- Is it because non-proxy providers don't want to run their bytecode enhancer= s to be spec compliant? > @ManyToOne results in default outer join eager fetch, should be lazy > -------------------------------------------------------------------- > > Key: ANN-430 > URL: http://opensource.atlassian.com/projects/hibernate/browse/A= NN-430 > Project: Hibernate Annotations > Type: Bug > Components: documentation, binder > Reporter: Christian Bauer > > > Documentation says: > > Association fetching > You have the ability to either eagerly or lazily fetch > associated entities. The fetch parameter can b= e set > to FetchType.LAZY or > FetchType.EAGER. EAGER will= try > to use an outer join select to retrieve the associated object, wh= ile > LAZY is the default and will only trigger a se= lect > when the associated object is accessed for the first time. EJBQL = also > has a fetch keyword that allows you to override > laziness when doing a particular query. This is very useful to im= prove > performance and is decided on a use case to use case basis. > > However, a simple @ManyToOne without any other attributes results in an e= ager join outer fetch. -- = This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --===============7263489449695837152==--