Hi,

I have an entity A which has a lazy 1-n relationship to an entity B
(i.e. a A holds a collection of B's) which in turn has an eager 1-n
relationship to an entity C. On the relationship between B and C I
want to use eager fetching using an outer join, which I specified on
the relationship configuration.

When I load an entity of type B this is indeed what happens: The
information for B and C are retrieved via a join.

However, when I load an entity A and later on initialize its
collection of B's a select is send for the B's and then a select for
the C's of each retrieved B is send. Why doesn't NHibernate use a join
in this case?

I read about this scenario in "Java Persistence with Hibernate" and as
far as I understand it should work. Does the NHibernate implementation
differ to the Hibernate implementation in this case?

Any reply is appreciated.

Best regards,
Ronald
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to