Thanks Chris, I was more curious about my decision to put all of the Codes, Intervals and Patterns into the same Class object. Does that seem ok to you?
Aside: I'm curious why you would suggest to use the ISet from Iesi over the IList A follow on to that would be ... my project is .NET 3.5, would it be better to use HashSet instead of ISet<T>? I remember reading somewhere that HashSet is geared for performance with Linq Thanks On Feb 8, 4:10 pm, Chris Marisic <[email protected]> wrote: > I would look at the Iesi Collections that are included with NHibernate > and instead of IList<Interval> use ISet<Interval> so you can take > advantage of the ImmutableSet and then in your mapping you'd have > something like > > Map.HasMany(x => x.NumericResponses) > .AsSet() > .Inverse() > .Cascade.All() > .CollectionType(typeof(ImmutableSet<Interval>)); > > I just coded this all free style so I'm not sure if it's 100% perfect > but it should be some what similar to this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en -~----------~----~----~----~------~----~------~--~---
