[hibernate-issues] [Hibernate-JIRA] Created: (HHH-4904) result of 'join fetch' query is incorrectly cached

[Geoff Crain (JIRA)]

result of 'join fetch' query is incorrectly cached
--------------------------------------------------

                 Key: HHH-4904
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4904
             Project: Hibernate Core
          Issue Type: Bug
          Components: caching (L2)
    Affects Versions: 3.3.2
         Environment: hibernate 3.3.2, EhCache 1.2.3, postgresql, mysql and hsql
            Reporter: Geoff Crain


Im not sure if this is either a bug, a missing option, or just an option that i can't find.

Im using hibernate 3.3.2, and EhCache 1.2.3.

I recently had an issue where objects in collections were getting dropped from the cache. After a long investigation, I found that it was because a "join fetch" query was being made on the parent object. http://docs.jboss.org/hibernate/core/3. ... ryhql.html

This meant that only a subset of the child elements were selected. If the collection was not already in the cache, the "incomplete" result of this query is put into it. Every subsequent call to the parent element (wanting the "full" set of children) would only get this incomplete version. When the incomplete version drops out of the cache (after 24 hours) everything goes back to normal.

So, is it a bug? Should hibernate (or ehcache) not be caching this "incomplete" collection? Or is there some way to tell hibernate that it is an incomplete collection _so_ that it doesnt get cached?

* If you believe this to be a bug, I will provide a working example. 
* If you think this is actually an EhCache bug, tell me and Ill raise it there

-- 
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