Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Is one supposed to be able to alter the type of a table whose definition
> has been used A composite in another table?
If the alter is of a kind that we can support, yes.
> Somewhat surprisingly to
> me, the following test did not produce an error:
> create table a( x text, y int);
> create table b( z a);
> insert into b values('(\'aaa\',3)');
> select * from b;
> alter table a add column q timestamp not null;
> select * from b;
This variant fails:
d=# alter table a add column qq timestamp default now() not null;
ERROR: cannot alter table "a" because column "b"."z" uses its rowtype
If you're unhappy about the "not null" part, the long and short of that
is that rowtypes don't carry along table constraints (yet), so it's
legal for b.z.q to show as null.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
