When developing using Fluent nHibernate, I notice that in relationships I can specify a property Fetchwith possible parameters Select(), Join()and Subselect().
I did a few searches and gave very little information. I found them in the documentation on nHibernate and in the free documentation on nHibernate, but it does a little different than giving my signatures, which does not help me too much.
I was wondering if there is any real explanation for what it is and what they actually do. I was very puzzled by myself. According to my own estimation, they seem to change their way of binding sites, linked to objects in the object graph, but I have yet to fully discern how they are changing, and some of them are optimal for any situation ...
I found this blog post (http://www.mkyong.com/hibernate/hibernate-fetching-strategies-examples/), which has some details, but I'm still very puzzled by the whole situation. I also saw other examples that say that use Select()is more optimal, but the argument behind it. Also, I found a post in (http://community.jboss.org/wiki/AShortPrimerOnFetchingStrategies) that targets the original Java Hibernate platform, but I assume the concept is the same. In this, my theory seems to be a bit overblown, as it focuses more on the lazy aspect of loading what they do, but I still haven't seen any really flat examples.
source
share