Actually, the bug was on both the LazyLoad and Nullable settings for the Many-To-One. Don't worry about my temporary workaround, I went ahead and checked in the fix. Grab the latest from the trunk and you should be good to go.
On Wed, Apr 15, 2009 at 12:13 AM, Hudson Akridge <[email protected]>wrote: > You just found a bug :) > I'll fix it, but in the mean time, change the order of your lazy/nullable > calls to be like so: > > References(x => x.Food).Cascade.None().Not.LazyLoad().Not.Nullable(); > > That should work for you temporarily. The problem is the "Nullable" on a > OneToMany isn't toggling the "Not" flag after it's called, thus, the second > time you were calling Not, just before your lazy load, it was actually doing > a "Not Not", or "True" ;) > > On Mon, Apr 13, 2009 at 8:06 AM, Jea <[email protected]> wrote: > >> >> As I get it the default convention is like in Nhibernate, lazy load is >> true by default. I want to turn of lazy load on a property, thought i >> could do it like >> >> References(x => x.Food).Cascade.None().Not.Nullable().Not.LazyLoad(); >> But it stills generates a Proxy. How do i turn it of? >> >> Regards >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
