Re: SET NULL / SET NOT NULL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Doug McNaught <doug(at)wireboard(dot)com>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SET NULL / SET NOT NULL
Date: 2002-02-22 02:56:07
Message-ID: 13279.1014346567@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Using the standard precedent above, how about

> ALTER TABLE blah ALTER COLUMN col SET NOT NULL;
> ALTER TABLE blah ALTER COLUMN col DROP NOT NULL;

This seems like a good choice if we are not too concerned about
compatibility with other DBMSes. (Which, for something like this,
I'm not; how many applications will be issuing programmed commands
like this?)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ruslan A Dautkhanov 2002-02-22 03:01:17 Re: date/time compatible problems in 7.2
Previous Message Marc G. Fournier 2002-02-22 02:38:58 In case anyone is intereated ... mail traffic today ...