> > > 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.
Folks, is this a valid reason for adding OR REPLACE to all CREATE object
commands?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026