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].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to