Can't get lazy loading to work

g_r_a_robinson@hotmail.co · **Joined:** Sat Sep 17, 2005 5:48 am **Posts:** 9

I've tried for days to get my countrys to not load the cities and states, however ive tried a few things and i dont seem to get anywhere. When I check the property values in my debugger, sure enough i can see everything.

Here's my xml file for countries:

Code:

<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.0" schema="dbo">
  <class name="DAL.Country, DAL" table="Countries" lazy="true">
    <id name="Id" type="Int32" column="country_id">
      <generator class="identity" />
    </id>
    <bag name="Cities" inverse="true">
      <key column="country_id" />
      <one-to-many class="DAL.City, DAL" />
    </bag>
    <property name="countryprefix" column="country_prefix" type="String" />
    <property name="countryname" column="countryname" type="String" />
    <bag name="States" inverse="true">
      <key column="country_id" />
      <one-to-many class="DAL.State, DAL" />
    </bag>
  </class>
</hibernate-mapping>

And my code:

Code:

session = Global.Factory;
IList countries = null;

Country country = new Country();
string query = "from DAL.Country";
countries = session.Find(query);
session.Close();

Can anyone see something I cant?

sergey · **Posted:** Sat Oct 01, 2005 6:16 am

First, you should add lazy="true" to your <bag> elements.
Second, looking at a property through the debugger might well cause the collection to initialize.

Guest · **Posted:** Thu Oct 06, 2005 9:17 pm

OK, I tried your first suggestion by setting the bag to have the lazy="true' property. Still no dice.

However i'm perturbed by the idea that my debugger would by overriding my lazy loading. And if i cant see it in my debugger how am i supposed to verify the values being returned (unless i write them all to screen) which I could do. Anyone know of this happening in the vs debugger.

paulh · **Posted:** Fri Oct 07, 2005 3:49 am

If you are using SQL Server, you can use the profiler to see when the SQL is hitting the database, otherwise you can turn on the SQL logging in NHibernate and again see that the SQL hits the database when you first access the collection.