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 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
