From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE TODO items |
Date: | 2004-05-06 19:04:32 |
Message-ID: | 2609.1083870272@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> What about rules/views/functions and who knows what else (domains?)
> might be dependant on the current type definition?
Yeah, I was just thinking about that this morning. We probably ought to
look for dependencies on the table rowtype as well as the individual
column.
But on the other side of the coin, should we actually reject the ALTER
if we see a function that uses the rowtype as a parameter or result
type? Without looking inside the function, we can't really tell if the
ALTER will break the function or not.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-05-06 19:23:26 | pgsql-server/src/backend port/sysv_shmem.c pos ... |
Previous Message | Robert Treat | 2004-05-06 19:02:02 | Re: ALTER TABLE TODO items |
From | Date | Subject | |
---|---|---|---|
Next Message | James Robinson | 2004-05-06 19:06:56 | Re: PostgreSQL pre-fork speedup |
Previous Message | Tom Lane | 2004-05-06 19:02:06 | Re: alter table alter columns vs. domains |