Is my understanding correct, that the following class and table design is not possible in NHibernate:
public class Parent
{
public virtual Guid Id { get; set; }
public virtual ISet<Child> Children { get; set; }
...
}
public class Child
{
public virtual Guid Id { get; set; }
...
}
table Parent { Id, ... }
table Child { Id, ParentId (not null), ... }
So notice the following:
- a one-to-many association between parent and child
- using an ISet
- no bidirectional association from Child back to Parent
- Child's ParentId column is not null