From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Rod Taylor" <pg(at)rbt(dot)ca>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE TODO items |
Date: | 2004-05-07 11:05:07 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA40184D0C4@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> FireBird: ALTER COLUMN <column> TYPE <type>
> DB2: ALTER COLUMN <column> SET DATA TYPE <type>.
> Oracle: MODIFY <column> <type>
> MSSQL: ALTER COLUMN <column> <type> <constraints>
> MySQL: Both Oracle and MSSQL
> Sap: MODIFY <column> <type>
>
> Spec: Nothing (obvious) on changing column types
>
> MODIFY is horrible. It seems to drop all constraints, defaults, etc that
> are not specified in the second definition. It is essentially a
> replacement of the column.
In Oracle MODIFY leaves omitted parts unchanged,
syntax is actually ALTER TABLE <table> MODIFY (<column> <type> <default> <constraint>)
I think the parentheses are optional if only one column is modified.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2004-05-07 11:41:56 | Re: Is there any method to keep table in memory at startup |
Previous Message | Gaetano Mendola | 2004-05-07 10:25:07 | Constraint not shown on \d ? |