Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>
Cc: pgsql-hackers(at)postgresql(dot)org, pgadmin-hackers(at)postgresql(dot)org, dpage(at)vale-housing(dot)co(dot)uk, peter_e(at)gmx(dot)net, lockhart(at)fourpalms(dot)org, Inoue(at)tpf(dot)co(dot)jp, wrstuden(at)netbsd(dot)org, oleg(at)sai(dot)msu(dot)su, scrappy(at)hub(dot)org
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER
Date: 2001-10-23 23:22:04
Message-ID: 200110232322.f9NNM4O28668@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgadmin-hackerspgsql-hackers
> Dear all,
> 
> Would it be possible to implement CREATE OR REPLACE VIEW / TRIGGER in 
> PostgreSQL 7.2?
> 
> 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?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-10-24 00:56:57
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER
Previous:From: Bruce MomjianDate: 2001-10-23 23:19:22
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER

pgadmin-hackers by date

Next:From: Bruce MomjianDate: 2001-10-24 00:56:57
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER
Previous:From: Bruce MomjianDate: 2001-10-23 23:19:22
Subject: Re: [HACKERS] CREATE OR REPLACE VIEW/TRIGGER

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group