-->
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: Join fetch complicates caching?
PostPosted: Sun Mar 20, 2005 3:05 pm 
Newbie

Joined: Thu Jan 06, 2005 8:05 am
Posts: 13
Since I'm not Hibernate expert, I just want to clearify something - if someone uses HQL left join fetching for obtaining entity with children entities, thus practicaly disabling lazy initialization for that collections in runtime, it brings complications when he enables second-level cache for that entity afterwards?

I understand that second-level cache will be utilized when entity is loaded by ID, but since I was forced change load(ID) into fetch join HQL query, this caching won't get utilized anymore, right? I am practicly forced to apply query cache for that HQL query in that case, right?

-Vjeran


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.