For me it's pretty obvious, if you are never going to allow the column to have an "unknown value", then define it NOT NULL to let the database guarantee that. Otherwise, nullable it is.
Terry Lee Tucker wrote:
Why would you never define a column as NOT NULL, or am I misunderstanding what you are saying?
On Friday 08 October 2004 06:07 am, Peter Eisentraut saith:
Briefly, you always do the first and never do the second.
-- dave
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
