R – How to tell NHibernate to map one-to-many relationship to List and not IList

nhibernateone-to-many

Can I somehow tell NHibernate to map my one-to-many relationship to a property which is of type List instead of the interface IList?

I know that NHibernate uses its own IList-implementation for lazy loading, but I don't need this feature. Instead I need a class that is serializable, which I cannot accomplish by using the IList interface instead of the concrete List-class.

Best Answer

The simple answer is no, you can't tell NHibernate to use List<T>. This earlier question discusses it in more detail.

The best article I could find on serializing NHibernate objects is targeted to WCF users.

Related Solutions

R – NHibernate one way, one-to-many, mapping question

The scenario you've described is just a basic one-to-many mapping. Here is the Fluent NHibernate mapping for this:

public class EmployeeMap : ClassMap<Employee>
{
    public EmployeeMap()
    {
        WithTable("Employee");
        HasMany(employee => employee.StatusList)
        .Cascade.All();
    }
}

You do not need to maintain a reference from EmployeeStatus back to Employee to achieve this.

R – Nhibernate: Make Many-To-Many Relationship to Map as One-To-One

Are you sure you mean a one-to-one? I've had so many people ask for one-to-one's when they really mean many-to-one's.

Anyway, short of changing your schema, the easiest thing is what you suggested; however, to make it a little cleaner, you can make the collections private so you're only exposing the two properties that fetch the first item. You can see the various methods in Fluent NHibernate for mapping private properties on the wiki.

Best Answer

Related Solutions

R – NHibernate one way, one-to-many, mapping question

R – Nhibernate: Make Many-To-Many Relationship to Map as One-To-One

Related Topic