[Hibernate-issues] [Hibernate-JIRA] Resolved: (HB-202) Fetched collections are not cached

[<leg...@at...>]

Message:

   The following issue has been resolved as DUPLICATE.

   Resolver: Gavin King
       Date: Wed, 16 Jul 2003 7:39 PM

I *think* this is already fixed in CVS.

Please test against the current CVS build of Hibernate.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-202


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-202
    Summary: Fetched collections are not cached
       Type: Improvement

     Status: Resolved
   Priority: Major
 Resolution: DUPLICATE

    Project: Hibernate2
   Fix Fors:
             2.0.2
   Versions:
             2.0 final

   Assignee: 
   Reporter: Peter Fassev

    Created: Wed, 16 Jul 2003 1:29 PM
    Updated: Wed, 16 Jul 2003 7:39 PM

Description:
If a collection is fetched together with an owner class using a query with the "left outher join fetch" construct, then the created collection is not added to the cache.

A tried a simple improvement and changed the PersistentCollectionType.getCollection() to add the collection to the cache:
....
PersistentCollection collection = session.endLoafingCollection(persister, id);
if (collection != null) {
  // this is the patch...
  persister.cache(id, collection, session);
  return collection.getCachedValue();
}
...

I am not shure if this is the right place for the patch and if this patch is enough, so a am ascing for improvement.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira