Yes that is the expected behavior. Turning off lazy loading for a -class- means that you won't get a proxy loaded. Its separate and different to lazy loading of a collection. Its perfectly valid to turn off lazy loading of a class, but leave lazy loading for one of its collections on. This would allow you to avoid: a) having to make all your members virtual, b) pulling half the database down from a single entity load :)
On Sat, Feb 27, 2010 at 12:01 AM, adrianhara <adrian.h...@iquestint.com>wrote: > Hi, > > A short question about lazy loading. Until today I had thought that > settings this.Not.LazyLoad() on a class mapping would effectively > disable lazy loading on its associations (HasMany() mappings). However > it doesn't seem to be the case, I have to also call > HasMany(...).Not.LazyLoad(). > > Is this the expected behavior? > > Thanks > > -- > 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<fluent-nhibernate%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/fluent-nhibernate?hl=en. > > -- 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.
