Re: Query performance problem

On Thursday 17 Mar 2005 7:35 pm, Richard Huxton wrote:

> Not necessarily. NOT NULL here helps to ensure you can add values
> together without the risk of a null result. There are plenty of
> "amount" columns that should be not-null (total spent, total
> ordered etc).

that makes sense - but is it necessary to have a not null constraint
when there is a default value?

--
regards
kg

http://www.livejournal.com/users/lawgon
tally ho! http://avsap.sourceforge.net
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!