Finally seen, the following message in the logs: Refusing to add to cache due to enabled filters
Hence the problem observed. I might need to implement the todo hint mentioned in NH src. On Thu, Mar 15, 2012 at 4:41 PM, carabosse <[email protected]> wrote: > Hi folks, > > **Situation: > - Traditional one to many parent-child relationship > - In the mapping caching is set for parent + child entities + > association > - NH 3.2 GA > > **Question: > Would/Should something like this > > QueryOver<Parent>() > .Fetch(p => p.Children).Eager > .Where(p => p.UID == someUID) > .Cacheable() > .SingleOrDefault() > > return a parent with its children collection initialized if the > request hits the query cache ? > > **My observation > - Children collection is lazy initialized when hitting the cache > - Looking at the cache statistics for the query show that only PK of > the parent is stored (multiple times, precisely as many as returned by > the generated join query) making me wonder if it is indeed complete, I > would eventually rather expect tuples such as (parent.UID, child.UID) > > Thanks for your time reading/answering. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
