From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at> |
Cc: | snpe <snpe(at)snpe(dot)co(dot)yu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: create or replace view |
Date: | 2002-11-15 15:54:59 |
Message-ID: | 20021115074954.N9290-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 15 Nov 2002, Zeugswetter Andreas SB SD wrote:
>
> > Problem is when I want change view (or functions) with a lot of dependecies
> > I must drop and recreate all dependent views (or functions) -
> > I want add only one column in view
> > I don't know if solution hard for that.
>
> I do not see how adding a column to a view would invalidate
> dependent objects. (Except an object that uses "select *", in which case
> the writer of the object explicitly states that he can cope with changing
> column count and order).
I'm not sure, but can all the places that currently save a plan deal with
getting a longer rowtype than expected? I'd guess so due to inheritance,
but we'd have to be absolutely sure. It'd also change the return type
for functions that are defined to return the composite type the view
defines.
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-11-15 16:43:47 | Re: pg_dump in 7.4 |
Previous Message | Tom Lane | 2002-11-15 15:23:03 | Re: Time to move on... |