| From: | "Rod Taylor" <rbt(at)zort(dot)ca> |
|---|---|
| To: | "Thomas Lockhart" <lockhart(at)fourpalms(dot)org>, "Doug McNaught" <doug(at)wireboard(dot)com>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SET NULL / SET NOT NULL |
| Date: | 2002-02-21 03:38:01 |
| Message-ID: | 009901c1ba89$2a048630$8001a8c0@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> ALTER TABLE tab ALTER COLUMN col DROP NOT NULL
>
> which does not seem particularly good; preserving the syntax from
table
> creation has to be TWTG. Do we really allow:
>
> CREATE TABLE FOO(BAR INT NULL)
Certainly does. I depend on that ability to override the standard
NULL / NOT NULL constraint that the domain may have to account for the
exception to the rule.
Actually, is that proper? Equally easy to disallow overrides, but
(since the books I have don't say) it seemed useful for people with
funny circumstances (like wanting to log a miss as well a hit).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-02-21 03:39:32 | Re: date/time compatible problems in 7.2 |
| Previous Message | Tom Lane | 2002-02-21 03:28:34 | Re: Selectively Compile psql |