Re: pg_views.definition

Поиск
Список
Период
Сортировка
От Gavin Sherry
Тема Re: pg_views.definition
Дата
Msg-id Pine.LNX.4.21.0207171143390.9723-100000@linuxworld.com.au
обсуждение исходный текст
Ответ на Re: pg_views.definition  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Ответы Re: pg_views.definition  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Список pgsql-hackers
On Wed, 17 Jul 2002, Christopher Kings-Lynne wrote:

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

I have written a patch for this. It is in an old source tree. I intend on
getting it together by august, along with create or replace trigger.

Gavin



В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Christopher Kings-Lynne"
Дата:
Сообщение: Re: Do we still need these NOTICEs?
Следующее
От: "Christopher Kings-Lynne"
Дата:
Сообщение: Re: pg_views.definition