Hello, I want to map a relationship that HasOne but I want for the parent-child one-to-many inverse to be effective.
I am finding the HasOne(...) to not quite fit the bill, that is the references seem to be reversed, referring literally to an id in the source table. However, that is not quite what we need nor want. When the parent goes away, we need for the child to also cascade. Technically that is hasMany(...) but how to we restrict that collection to just one element, ALWAYS? Better if that could be done if possible in a mapping. Although at this point, I am wondering that's not a modeling and/or business or controller operation. Thoughts? Insights? Thanks! Best, Michael W. 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/fluent-nhibernate/5bbd583e-d9a4-475c-b51b-25108d9948bfn%40googlegroups.com.
