From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Thomas Lockhart" <lockhart(at)fourpalms(dot)org> |
Cc: | "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-21 03:52:56 |
Message-ID: | GNELIHDDFBOCMGBFGEFOKEIACBAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The SQL spec will not help us here, since it doesn't define such a
> capability AFAICT. We might do worse than to look at Or*cle's
> implementation, which appears to involve a MODIFY keyword.
>
> I find this in the Or*cle 8i documentation examples:
>
> The following statement alters the EMP table and defines and
> enables a NOT NULL constraint on the SAL column:
>
> ALTER TABLE emp
> MODIFY (sal NUMBER CONSTRAINT nn_sal NOT NULL);
>
> The docs are opaque enough that I can't actually figure out a BNF
> definition for ALTER TABLE MODIFY, and I don't have a working
> installation to experiment against. Can any Or*cle users here
> enlighten us?
I've already posted the Oracle and MSSQL spec to the list here - just check
one of my earlier posts with this subject...
A good place to ask questions is comp.databases.oracle.misc
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Ruslan A Dautkhanov | 2002-02-21 04:00:58 | Re: date/time compatible problems in 7.2 |
Previous Message | Tom Lane | 2002-02-21 03:47:58 | Re: SET NULL / SET NOT NULL |