From: Tom Lane <tgl@sss.pgh.pa.us>
To: mhh@mindspring.com
Cc: Joel Burton <jburton@scw.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re: [SQL] Rules with Conditions: Bug, or Misunderstanding
Date: Sat, 02 Dec 2000 00:18:39 -0500
Message-ID: <16036.975734319@sss.pgh.pa.us> (raw)
In-Reply-To: <00120121475101.09339@jupiter.hollomon.fam>
References: <3A255246.21430.688927F3@localhost>
<00113022072200.00743@jupiter.hollomon.fam>
<1984.975648802@sss.pgh.pa.us>
<00120121475101.09339@jupiter.hollomon.fam>
Mark Hollomon <mhh@mindspring.com> writes:
> I think it would be better to move the test further down, to just before we
> actually try to do the update/insert. Maybe into the heap access routines as
> suggested by Andreas.
I'm worried about whether it'll be practical to generate a good error
message from that low a level.
Looking at it from the DBA's viewpoint rather than implementation
details, I haven't seen a good reason *why* we should support
conditional rules for views, as opposed to an unconditional rule with
multiple actions. Seems to me that writing independent rules that you
hope will cover all cases is a great way to build an unreliable system.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, mhh@mindspring.com, jburton@scw.org, pgsql-hackers@postgresql.org
Subject: Re: [SQL] Rules with Conditions: Bug, or Misunderstanding
In-Reply-To: <16036.975734319@sss.pgh.pa.us>
References: <3A255246.21430.688927F3@localhost> <00113022072200.00743@jupiter.hollomon.fam> <1984.975648802@sss.pgh.pa.us> <00120121475101.09339@jupiter.hollomon.fam> <16036.975734319@sss.pgh.pa.us>
* 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