I've got a strange problem with some of my mappings...
Pretty much everything (both collections and individual entities) are set to lazy load. While still in the same session I'm getting this strange behaviour where a child of an entity will not evaluate to null but will also not appear to actually exist.
When examining one of these "non existent" entities using the VS.NET debugger the object type is showing as two empty braces '{}'.
Eg:
Code:
<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.0" namespace="Framework.Core.Entities" assembly="Framework.Core">
<class name="User" table="Users" lazy="true" where="Deleted = 0">
<id name="id" column="UserID" unsaved-value="0" access="field">
<generator class="native" />
</id>
<version name="version" column ="Version" access="field"/>
<property name="username" column="Username" length="50" access="field"/>
<property name="password" column="Password" length="50" access="field"/>
<many-to-one name="customer" column="CustomerID" class="Customer" access="field"/>
</class>
</hibernate-mapping>
with the other half:
Code:
<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.0" namespace="Framework.Core.Entities" assembly="Framework.Core">
<class name="Customer" table="Customers" lazy="true" where="Deleted = 0">
<id name="id" column="CustomerID" unsaved-value="0" access="field">
<generator class="native" />
</id>
<version name="version" column="Version" access="field"/>
<property name="name" column="Name" length="50" access="field"/>
<bag name="users" lazy="true" access="field" where="Deleted = 0" inverse="true">
<key column="CustomerID" />
<one-to-many class="User" />
</bag>
</class>
</hibernate-mapping>
In this case I'm seeing the customer field of the User object as {} even though the correct data exists in the database for the object. I would have expected to see a proxy...
Removing the lazy attribute from the Customer object will cause the problem to go away, however I don't the whole object tree to load as we have quite a complex recursive relationship between many objects, so a lot of records would end up loaded.
I'm seeing this quite often - does anyone know why this might be happening?
Cheers,
Symon.
Login
FAQ
Search
