I can think on only one reason for having such thing; using an entity as viewmodel.
I think you have an scenario like this; A null in the entity property must not be even possible, a null in the vm is very possible, the user forgot to enter a value... 2010/9/18, ronnieoverby <[email protected]>: > I'm learning to use NHibernate validator and it's Fluent API > (Loquacious). > > I have noticed is that I can't set an integer property or nullable int > property (int?) to be not nullable. Well, why not? > > In a database, an integer column can have null values. Even worse, > when I generate DDL using SchemaExport, the integer column wont be > picking up that non-nullabity (unless I express it in the Nhibernate > mappings). > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" 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/nhusers?hl=en. > > -- Enviado desde mi dispositivo móvil -- You received this message because you are subscribed to the Google Groups "nhusers" 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/nhusers?hl=en.
