That's most certainly not by design, your second example is how it should work. I'll verify whether this is happening against our model/1.0 branch.
On Mon, Aug 3, 2009 at 2:49 PM, Guido Ziliotti <[email protected]>wrote: > References(x => x.Categoria) > .Not.LazyLoad() > .Nullable() ; > > Produces a "not null" column. So it looks like > > .Not > > affects > > .Nullable() > > line too. > > This is probably by design but a bit misleading in my opinion. > > > References(x => x.Categoria) > .Not.LazyLoad() > .Not.Nullable() ; > > produces a "null" column. > > Personally I'prefer the contrary to happen. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
