Hello there.
Using trunk.
I'm seeing a strange behaviour on a set mapping.
I used to have a mapping like this:
<class A
<cache usage="read-only"/>
<set B>
<one-to-many class="X"/>
</set>
</class>
My entity A is perfectly cached and retrieved from 2. level cache
(seen via NHProf) and the set of X's (150 elements) is fetched in one
go afterwards.
Now to the strange behaviour:
I found out that its possible to cache a set as well and therefore
added this to the mapping:
<class A
<cache usage="read-only"/>
<set B>
<cache usage="read-only"/> <---
caching of the set
<one-to-many class="X"/>
</set>
</class>
Now 150 elements of the set are loaded in a N+1 fashion one by one via
their id !!! (and they are not cached)
Is this a bug or am I missing something ??
Kind regards
Carsten
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
