-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: FetchType.EAGER vs LazyCollectionOption.FALSE
PostPosted: Thu May 03, 2007 8:33 pm 
Newbie

Joined: Fri Apr 15, 2005 7:52 pm
Posts: 13
Hi,

When switiching to annotations it seems that there is a disctinction between using fetch=FetchType.EAGER vs LazyCollection(LazyCollectionOption.FALSE) - at least in one-to-many associations using a JoinColumn. Using LazyCollectionOption.FALSE results in usual performance/behavior similar to when using lazy="true" with xdoclet. Using FetchType.EAGER however results in larger SQL queries and slowdown. As far as hibernate is concerned, what exactly is the difference between using the EJB3 OneToMany property fetch=FetchType.EAGER and using the hibernate annotation LazyCollection(LazyCollectionOption.FALSE) on a OneToMany association (using a JoinColumn)? TIA!


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.