Re: Modifying NOT NULL Constraint - Mailing list pgsql-hackers

From Chris Bitmead
Subject Re: Modifying NOT NULL Constraint
Date
Msg-id 394727C0.7493DCF@nimrod.itg.telecom.com.au
Whole thread Raw
In response to Modifying NOT NULL Constraint  ("Dan Wilson" <phpPgAdmin@acucore.com>)
List pgsql-hackers
Tom Lane wrote:

> What do you think should happen if there are null values?  Refuse the
> command?  Delete the non-compliant rows?  Allow the rows to remain
> even though the column is now nominally NOT NULL?

I would vote for refuse the command. It enforces the integrity of the
data.
You can always do an appropriate update command first if you think there
are 
nulls in there.


pgsql-hackers by date:

Previous
From: "Dan Wilson"
Date:
Subject: Re: Modifying NOT NULL Constraint
Next
From: Michael Robinson
Date:
Subject: Re: Big 7.1 open items