From: Hannu Krosing <hannu@tm.ee>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: elein <elein@varlena.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Adding MERGE to the TODO list (resend with subject)
Date: Tue, 11 May 2004 09:59:42 +0300
Message-ID: <1084258782.4709.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200405102126.i4ALQ5f23657@candle.pha.pa.us>
References: <200405102126.i4ALQ5f23657@candle.pha.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: hannu@tm.ee, pgman@candle.pha.pa.us, chriskl@familyhealth.com.au, alvherre@dcc.uchile.cl, elein@varlena.com, pgsql-hackers@postgresql.org
Subject: Re: Adding MERGE to the TODO list (resend with subject)
In-Reply-To: <1084258782.4709.7.camel@localhost.localdomain>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox