| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SET NULL / SET NOT NULL |
| Date: | 2002-02-21 02:12:19 |
| Message-ID: | 3.0.5.32.20020221131219.03565740@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 09:59 15/02/02 +0800, Christopher Kings-Lynne wrote:
>
>ALTER TABLE blah ALTER COLUMN col SET [NULL | NOT NULL]
>
I'm not too fond of 'SET NULL' - the syntax implies the column is being set
to NULL. But I agree with the rest given we already have ALTER
TABLE...ALTER COLUMN, I'd vote for:
ALTER TABLE blah ALTER COLUMN col [ALLOW NULL | NOT NULL]
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug McNaught | 2002-02-21 02:18:49 | Re: SET NULL / SET NOT NULL |
| Previous Message | Tatsuo Ishii | 2002-02-21 01:08:33 | Re: UTF-8 data migration problem in Postgresql 7.2 |