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
-~----------~----~----~----~------~----~------~--~---
