I have a class Contact (base class),a class called Customer and a class called Supplier. Customer and supplier class both derive from Contact.
Customer has a 0..n relat
This is done like this:
Create your class like this:
public class Customer : Contact
{
private ISet _orders = new HashedSet();
public Collection Orders
{
return new List(_orders);
}
// NOrmally I would return a ReadOnlyCollection instead of a Collection
// since I want to avoid that users add Orders directly to the collection.
// If your relationship is bi-directional, then you have to set the other
// end of the association as well, in order to hide this for the programmer
// I always create add & remove methods (see below)
public void AddOrder( Order o )
{
if( o != null && _orders.Contains(o) == false )
{
o.Customer = this;
_orders.Add(o);
}
}
}
in your mapping, you specify this:
Since you use inheritance, you should definitly have a look at the different posibilities regarding inheritance-mapping in NHibernate, and choose the strategy that is best suited for your situation: inheritance mapping
Regarding set & bag semantics: - when you map a collection as a set, you can be sure that all the entities in the mapped collection, are unique. That is, NHibernate will make sure that, while reconstituting an instance, the collection will not contain duplicates. - when you map the collection as a bag, it is possible that your collection will contain the same entity more then once when loading the object from the DB.