aaahhh ~90/95% of not-nullable... have you ~90/95% of references in each domain obj ? perhaps I saw even more of not nullable but it is because they are int, long, bool, enum, decimal, DateTime... and there is no way to see a null in the DB (obviously when Table-per-class is used).
btw the link for proposal is: http://216.121.112.228/browse/NH <http://216.121.112.228/browse/NH> 2010/3/8 kor <[email protected]> > we don't use Table-per-class-hierarchy :) at the moment ~90/95% of > our columns are not-null, > the world is not perfect, a not-null constraint helps to reduce bugs > (and give a better readibility to the db). > > in my opinion is analogous to why check for null argument reference? > you don't need it, it's the client code which must pass you only not- > null reference.. > > -- > 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]<nhusers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- Fabio Maulo -- 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.
