From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Archana Sundararam <archnasr(at)yahoo(dot)com> |
Subject: | Re: ALTER TABLE should change respective views |
Date: | 2009-05-05 14:10:08 |
Message-ID: | 15445.1241532608@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> And this could then also change the return type of foo(), thus changing the
> row type of the view and would thus propogate up to other views. And so if
> you have "many views", as you say, this could become a great mess. You could
> probably define and implement a solution, but it would be very confusing and
> risky to use.
The SQL committee has also historically chosen to punt on such things.
Note the long-established rule that "*" is expanded at view definition
time (so adding columns doesn't change views). I also see a flat
prohibition on *any* view reference in the newly added SET DATA TYPE
command (SQL:2008 11.17 <alter column data type clause>):
7) C shall not be referenced in the <query expression> of any view descriptor.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2009-05-05 14:13:43 | Re: bytea vs. pg_dump |
Previous Message | Kevin Grittner | 2009-05-05 14:05:47 | Re: bytea vs. pg_dump |