Hello,
I have a case where I started with a self-referencing parent/child
relationship, which started well enough. Tables were mapping and I was
migrating my database okay.
I am maturing the model now, and shifting gears to away from MySQL
towards SQL Server, and finding that the self-referencing parent/child
doesn't work so well, especially where cascades are involved.
So, I am considering normalizing the parent/child to a separate
"family tree" table. Okay, in and of itself. However, how do I capture
that now in terms of fluent mapping?
Say, the domain is something like:
class A
{
public virtual A Parent { get; set; }
public virtual IList<A> Children { get; set; }
}
That's what I am aiming for, but now with the tables being:
A
============
|ID|
A_TREE
============
|PARENT_ID|CHILD_ID|
I could say HasMany Children, References Parent, but now with the tree
table, not so sure of that.
Best regards,
Michael Powell
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to fluent-nhibernate+unsubscr...@googlegroups.com.
To post to this group, send email to fluent-nhibernate@googlegroups.com.
Visit this group at http://groups.google.com/group/fluent-nhibernate.
For more options, visit https://groups.google.com/d/optout.
