From: Steve E. (JIRA) <no...@at...> - 2006-06-28 05:43:00
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole closed HHH-1543: ------------------------------- Fix Version: (was: 3.2.0) Resolution: Won't Fix fetching is a hint, not a guarentee > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |