-->
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: Overriding a default fetch strategy of subselect
PostPosted: Tue Jul 10, 2007 9:49 am 
Newbie

Joined: Wed Jan 17, 2007 4:07 pm
Posts: 3
We are trying to provide a way to programmatically change the fetch strategy being utilized. We found this to be easy enough with the Criteria API. I know there is no way to specify subselect this way, so I tried to set fetch=subselect in my mapping file under the impression that the client app could simply pass in FetchMode.SELECT, JOIN, or DEFAULT to specify which mode to use. This works fine when specifying JOIN. Also, specifying DEFAULT does result in subselect, however, when choosing SELECT, we still get a subselect. It's like the select mode won't override subselect. Is this the correct behavior and if so, is there anything we can do to make it possible for the client app to specify all three fetch modes?


Top
 Profile  
 
 Post subject:
PostPosted: Tue Aug 07, 2007 12:48 pm 
Newbie

Joined: Tue Aug 07, 2007 12:46 pm
Posts: 4
I am having the exact same problem. I believe FetchMode should be either augmented, fixed, or at least the typos in the Javadoc should be fixed.


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.