Re: create or replace view

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "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 08:24:19
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA4961EF5@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 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).

Thus I think "create or replace" should work in this case regardless of
what definition for "create or replace" finds a consensus, no ?

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Evgen Potemkin 2002-11-15 09:37:42 Proposal of hierarchical queries, a la Oracle
Previous Message Dave Page 2002-11-15 08:10:22 Re: Time to move on...