-->
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: Hibernate Fetching Strategies Affects On Second Level Cache
PostPosted: Tue Aug 25, 2009 2:06 pm 
Newbie

Joined: Tue Aug 25, 2009 1:59 pm
Posts: 1
Hello and thanks for taking the time to read my question.

I wanted to be able to dynamically setup the collection fetch style (select/join) at runtime but I see I can't do that yet. As an alternative I was thinking of using a reasonable Batch Fetching to help some of that problem.

http://docs.jboss.org/hibernate/stable/core/reference/en/html/performance.html#performance-fetching-batch

My question is: If I set a default fetch size on the class (in hbm.xml) does it completely bypass the second level cache? For example:

If I have an un-initialized collection but all of its elements exist in the second-level cache, will it execute the batch-fetch anyway on access or is it smart enough to check the second-level cache first AND THEN batch-fetch if it tries to load an object that hasn't been cached yet?

Thanks!


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.