Re: Modifying NOT NULL Constraint

From: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dan Wilson <dan_wilson(at)geocities(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Modifying NOT NULL Constraint
Date: 2000-06-14 06:35:45
Message-ID: 394727C0.7493DCF@nimrod.itg.telecom.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Robinson 2000-06-14 08:24:05 Re: Big 7.1 open items
Previous Message Dan Wilson 2000-06-14 06:33:29 Re: Modifying NOT NULL Constraint