Re: pg_views.definition

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jan Wieck" <JanWieck(at)Yahoo(dot)com>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_views.definition
Date: 2002-07-17 01:31:29
Message-ID: GNELIHDDFBOCMGBFGEFOMECOCDAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > We do, but as soon as you break the view by dropping an underlying
> > object it fails to reconstruct. So having the original view definition
> > at hand could be useful for some ALTER VIEW RECOMPILE command.
>
> Note that the assumptions underlying this discussion have changed in
> CVS tip: you can't break a view by dropping underlying objects.
>
> regression=# create table foo(f1 int, f2 text);
> CREATE TABLE
> regression=# create view bar as select * from foo;
> CREATE VIEW
> regression=# drop table foo;
> NOTICE: rule _RETURN on view bar depends on table foo
> NOTICE: view bar depends on rule _RETURN on view bar
> ERROR: Cannot drop table foo because other objects depend on it
> Use DROP ... CASCADE to drop the dependent objects too

Hrm - looks like we really need CREATE OR REPLACE VIEW...

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-07-17 01:43:45 Re: Do we still need these NOTICEs?
Previous Message Hiroshi Inoue 2002-07-16 23:37:13 Re: DROP COLUMN