Child collections are not being stored in the second level cache
Description
Logging showed that child collections were being loaded from the database with every page hit, although individual entities are successfully stored in the cache. This happens regardless of whether or not the child collections are also being lazy loaded.
Further investigation indicates that NHibernate is looking for child collections in the cache but not saving them.
Environment
Windows XP Pro, .net 1.1, NHibernate 0.6.0.0, NHibernateContrib 0.6.0.0 modified to correct issue NH-194
Okay, I've downloaded the latest sources from CVS and it seems to work fine now.
There's one other related issue that I have noticed though. When I try to load a non-existent object using ISession.Get(), a subsequent request for the same object results in another round trip to the database. Would it be worth considering adding some kind of marker object to the cache in this case to flag that the item wasn't found?
MikeM February 6, 2005 at 5:45 PM
Code was committed to cvs - I believe it is fixed there by stepping through it during the test run.
Need to find a better way than stepping through code to verify test is running - look at raising events from cache for hits, misses, etc...
MikeM February 5, 2005 at 11:54 PM
Did alot of digging into how collections are being cached. In the middle of debugging, but it definitely is a problem as described.
Logging showed that child collections were being loaded from the database with every page hit, although individual entities are successfully stored in the cache. This happens regardless of whether or not the child collections are also being lazy loaded.
Further investigation indicates that NHibernate is looking for child collections in the cache but not saving them.