From: Kenneth Gonsalves <lawgon@thenilgiris.com>
To: Richard Huxton <dev@archonet.com>
Cc: weberp@paradise.net.nz
Cc: pgsql-sql@postgresql.org
Subject: Re: Query performance problem
Date: Fri, 18 Mar 2005 10:49:47 +0530
Message-ID: <200503181049.47566.lawgon@thenilgiris.com> (raw)
In-Reply-To: <42398EB9.2050707@archonet.com>
References: <200503172120.20676.weberp@paradise.net.nz>
<200503171801.19412.lawgon@thenilgiris.com>
<42398EB9.2050707@archonet.com>
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
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: lawgon@thenilgiris.com, dev@archonet.com, weberp@paradise.net.nz
Subject: Re: Query performance problem
In-Reply-To: <200503181049.47566.lawgon@thenilgiris.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox