You guessed correct. Not that it was really obvious a place to put it, but there's details of the method changes in the commit message. Two commits were involved:
r238: Update to make booleans use the NUnit style Not inverter property, this way we don't have to implement both variations (and forget as we did with LazyLoad). As a result this change adds the positive or negative variants to any operations that were missing them. Changes are: NotLazyLoaded() -> Not.LazyLoad() IsInverse() -> Inverse() and Not.IsInverse() AutoImport(bool) -> AutoImport() and Not.AutoImport() WithUniqueConstraint() -> Unique() and Not.Unique() CanNotBeNull() -> Not.Nullable() and Nullable() and r242: Brought Map in line with the recent Not changes. Changes made: CanNotBeNull() -> Not.Nullable() and Nullable() WithUniqueConstraint() -> Unique() and Not.Unique() AsReadOnly() -> ReadOnly() and Not.ReadOnly() ValueIsAutoNumber() -> AutoNumber() and Not.AutoNumber() On Sun, Feb 1, 2009 at 6:41 PM, m4bwav <[email protected]> wrote: > > I suppose it could be not null by default. > > On Feb 1, 12:39 pm, m4bwav <[email protected]> wrote: > > A couple changes were made in the syntax in the last update, so I'm > > curious about the not null constraint. > > > > I assume that a statement in a fluent class map code file that used to > > be like: > > > > "Map(x => x.Username).Unique().CanNotBeNull();" > > > > is now, > > > > "Map(x => x.Username).Unique().Not.Nullable();" > > > > Or did I guess that one wrong? > > > > Thanks, > > Mark > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
