Subject: Re: Adding MERGE to the TODO list (resend with subject)
From: Hannu Krosing <hannu@tm.ee>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>,
	Alvaro Herrera <alvherre@dcc.uchile.cl>, elein <elein@varlena.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
In-Reply-To: <200405102126.i4ALQ5f23657@candle.pha.pa.us>
References: <200405102126.i4ALQ5f23657@candle.pha.pa.us>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1084258782.4709.7.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Tue, 11 May 2004 09:59:42 +0300

Bruce Momjian kirjutas T, 11.05.2004 kell 00:26:
> Hannu Krosing wrote:
> > Bruce Momjian kirjutas E, 10.05.2004 kell 06:58:
> > > Added to TODO:
> > > 
> > > 	* Add MERGE command that does UPDATE, or on failure, INSERT
> > 
> > perhaps the issue raised about BEFOR/AFTER INSERT/UPDATE TRIGGERS and
> > RULES should get a mention in the TODO (... needs to be discussed, or
> > somesuch ...)
> 
> Uh, what was the issue there?

I think it is not well defined, which triggers should be run. For
example, should BEFORE UPDATE trigger be run and should INSERT be done
if BEFORE UPDATE forbids UPDATE. 

Also how should the rule system act - should there be separate rules for
MERGE, or/and should MERGE be expanded by both UPDATE and INSERT rules.

---------------
Hannu