Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine
Date
Msg-id [email protected]
Whole thread Raw
In response to ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine  ("Dmitry Koterov" <[email protected]>)
Responses Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine
List pgsql-hackers
On Thu, Dec 4, 2008 at 9:53 AM, Dmitry Koterov <[email protected]> wrote:
> Hello.
>
> I can successfully ALTER a NON-EMPTY table (ct) which ROWTYPE is used as a
> column type for another table (dt):
>
> CREATE TABLE ct (id INTEGER);
> CREATE TABLE dt (id INTEGER, c ct);
>
> INSERT INTO dt VALUES(1, '(666)');
> SELECT * FROM dt;
> -- (1, '(666)')
>
> ALTER TABLE ct ADD COLUMN n INTEGER;
> SELECT * FROM dt;
> -- (1, '(666,)')
>
> You see, '(666,)' means that the new field is added successfully.
>
>
> But, if I declare ct as a COMPOSITE type (not a table), it is not permitted
> to ALTER this type (Postgres says that there are dependensies on ct).
> Why?

Because of this there is no reason to ever use 'create type'....always
use 'create table'.  'alter type' can't add/remove columns anyways.

merlin


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: In-place upgrade: catalog side
Next
From: tmp
Date:
Subject: Re: Optimizing DISTINCT with LIMIT