| From: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SET NULL / SET NOT NULL |
| Date: | 2002-03-22 06:54:10 |
| Message-ID: | 20020322065410.GA12161@rice.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 22, 2002 at 02:34:57PM +0800, Christopher Kings-Lynne wrote:
> > > Do we want the above syntax, or this syntax:
> > >
> > > ALTER TABLE blah ALTER COLUMN col SET NOT NULL;
> > > ALTER TABLE blah ALTER COLUMN col SET NULL;
> >
> > My only objection to the second command is that it's plain wrong. You
> > don't set anything to NULL, so don't make the command look like it.
>
> So then how is it any more wrong than SET NOT NULL?
>
> It should almost be ADD NOT NULL ...
Hmm, there's this SQL92 keyword here: what do people thing of NULLABLE?
SET NOT NULLABLE
SET NULLABLE
Ross
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-03-22 07:06:36 | Re: notification: pg_notify ? |
| Previous Message | Bruce Momjian | 2002-03-22 06:54:01 | Re: Problem with reloading groups in pg_hba.conf |