Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER - Mailing list pgadmin-hackers

From Bill Studenmund
Subject Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER
Date
Msg-id Pine.NEB.4.33.0110221132320.6662-100000@vespasia.home-net.internetconnect.net
Whole thread Raw
Responses Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER  (Peter Eisentraut <peter_e@gmx.net>)
List pgadmin-hackers
On Tue, 23 Oct 2001, Bruce Momjian wrote:

> > Dear all,
> >
> > Would it be possible to implement CREATE OR REPLACE VIEW / TRIGGER in
> > PostgreSQL 7.2?

Probably not, it's rather late in the cycle (isn't beta imminent?). Oh,
I'd vote for "OR REPLACE" as there's already an opt_or_replace
non-terminal in the parser. Adding an optional "OR DROP" might displease
yacc, and also follows in the same vein as what we have for CREATE
FUNCTION.

> > Alternatively, could someone implement CREATE OR DROP VIEW / TRIGGER? These
> > features are needed for pgAdmin II (we could also provide a patch for
> > PhpPgAdmin). If this cannot be implemented in PostgreSQL, we will go for
> > pseudo-modification solutions (which is definitely not a good solution).
>
> Our current CREATE OR REPLACE FUNCTION perserves the OID of the
> function.  Is there similar functionality you need where a simple
> DROP (ignore the error), CREATE will not work?

If possible, it's nice to not have commands whose error codes you ignore.
That way if you see an error, you know you need to do something about it.

Take care,

Bill


pgadmin-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER