Is not a matter of initialization but a matter of access. probably you are trying to access to the field from a no virtual property and the instance you are using is a proxy.
On Thursday, April 5, 2012 6:29:25 PM UTC-3, Tim Scott wrote: > > After upgrading to NH 3.2.0.4000 we now get an exception here because > orderDates is null. > > foreach (var orderDate in orderDates) > > It's declared thusly: > > protected IList<OrderDate> orderDates = new List<OrderDate>(); > > And mapped like this: > > <bag name="orderDates" access="field.camelcase" inverse="true" > lazy="true" cascade="all-delete-orphan" > > <key column="OrderId" /> > <one-to-many class="OrderDate" /> > </bag> > > A few frames down in the stack trace is: > > at NHibernate.Proxy.DefaultLazyInitializer.Intercept(InvocationInfo > info) > > There are no matching order date rows in the database. > > Why is NH lazy initializing this collection to null instead of > empty? How can I fix? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/U_F8ftaNMjAJ. 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/nhusers?hl=en.
