@jason, thanks, i will try but the problems seems to be to manage when not-null=false is used. in this application there're other applications wich use the db without nhibernate, if i have also db cosntratins it's more safe
@fabio, for me it's a waste of time if samebody will implement it, also becouse seems that i'm the only one that uses a lot the not-null constraint at db level. anyhow with fluent it's possible so is only a problem for dinosaurs as me wich works with net 2.0. the 90/95% is referred to both references and properties (mainly properties). waht do you mean with 'there is no way to see a null in the DB '? if it's becouse with nhibernate struct properties cannot be mapped to null (but string yes) i what the not-null constraint becouse same data insertion is made also with ado.net (there're same massive batch insertion) and by same store procedures/db trigger -- 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.
