I'm have a State class the represents states of the unions. It is generally a many-to-one to other classes. When i use Enumerable() for some reason, it runs a query per each record in the database. I'm just trying to get all the states, but sql profiler shows it getting just the ID for all the states, then running one query per state to get all the other information, resulting in 50+ queries.

My code is:

Session..CreateQuery("FROM State ORDER BY Abbreviation ").Enermable()

Here's my mapping:

<class name="State" table="State">
<!-- Primary key -->
<id column="StateId" type="int" name="ID" access="field.camelcase-underscore">
<generator class="native">
</generator>
</id>

<!-- One-To-Many relationships -->
<bag name="RegistrantList" inverse="true" lazy="true" cascade="all-delete-orphan" >
<key column="StateId" />
<one-to-many class="Registrant" />
</bag>
<bag name="StateSandlotprofilelist" inverse="true" lazy="true" cascade="all" >
<key column="StateID" />
<one-to-many class="SandlotProfile" />
</bag>
<bag name="IssuingstateSandlotprofilelist" inverse="true" lazy="true" cascade="all" >
<key column="IssuingStateID" />
<one-to-many class="SandlotProfile" />
</bag>

<!-- Standard Properties/Fields -->
<property column="Name" type="System.String" name="Name" not-null="true" access="field.camelcase-underscore" />
<property column="Abbreviation" type="System.String" name="Abbreviation" not-null="false" access="field.camelcase-underscore" />
</class>

That is exactly what Enumerable() is designed to do. See docs here:
http://www.hibernate.org/hib_docs/nhibe ... a-querying

Use List() instead.

You're my hero lately!

So I was using enmerable() because I thought it would eliminate duplicate objects from my result set. For instance, if I have this:

SELECT c
FROM Customer
JOIN FETCH c.Orders

I thought that would give me a bunch of duplicate customers, because i'm asking it to preload the Orders collection. A normal SQL join would do that--it would return repeating customer fields, and then the order fields.

Does this make sense?

Thanks,
Craig

If my guess is correct, the HQL you need is this:

It should fetch the Orders via a left join and also eliminates the duplication of Customers.