On Aug 20, 1:19 pm, Nick Webb <nwe...@gmail.com> wrote: > To toss in my $0.02, also having had this issue come up, I offer that one > can easily handle the mappings in this case by specifying the columns for > each collection of the same type. In my case, I had a convention handling > the first, and only the second required an override on the column name be > set - this resolved the issue.
Could you post some code snippets of the convention and the override that illustrate this approach? > However, I disagree with the concept that one can build an object model and > expect nhibernate to figure out how to make such a model work in a database Well, I certainly don't expect it to be able to map every concievable object model to a database. But it already does an amazingly good job of auto mapping many standard OO constructs - far better than any other tool I'm aware of. Maybe this is just a happy accident, but it was the main reason I chose to use FNH over the alternatives. -Tom -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to fluent-nhibern...@googlegroups.com. To unsubscribe from this group, send email to fluent-nhibernate+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
