-->
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.  [ 2 posts ] 
Author Message
 Post subject: many to one default fetch strategy
PostPosted: Wed Apr 12, 2006 11:31 pm 
Newbie

Joined: Mon Apr 03, 2006 1:38 am
Posts: 11
Hi guys,

Just wondering why the default fetch strategy for a <many-to-one> association mapping is sequential select as opposed to outer join fetching? I thought outer join fetching would be faster for most applications because it means less communication between the application server and the web server. Am I wrong in thinking that?


Top
 Profile  
 
 Post subject: Re: many to one default fetch strategy
PostPosted: Fri Apr 21, 2006 2:11 am 
Newbie

Joined: Wed Mar 29, 2006 2:24 am
Posts: 14
tjal wrote:
Hi guys,

Just wondering why the default fetch strategy for a <many-to-one> association mapping is sequential select as opposed to outer join fetching? I thought outer join fetching would be faster for most applications because it means less communication between the application server and the web server. Am I wrong in thinking that?


i thought so too but then i realized maybe they favor the minimalist approach, we don't want all those data unless we need them...


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

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.