From: Mark Hollomon <mhh@mindspring.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Joel Burton <jburton@scw.org>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Re: [SQL] Rules with Conditions: Bug, or Misunderstanding
Date: Thu, 30 Nov 2000 22:07:22 -0500
Message-ID: <00113022072200.00743@jupiter.hollomon.fam> (raw)
In-Reply-To: <19579.975544973@sss.pgh.pa.us>
References: <3A255246.21430.688927F3@localhost>
<19579.975544973@sss.pgh.pa.us>
On Wednesday 29 November 2000 19:42, Tom Lane wrote:
>
> Hm. Perhaps the "cannot update view" test is too strict --- it's not
> bright enough to realize that the two rules together cover all cases,
> so it complains that you *might* be trying to update the view. As the
> code stands, you must provide an unconditional DO INSTEAD rule to
> implement insertion or update of a view.
The idea was to check just before the update occurred to see if the
destination was view. Maybe the test is too high up, before all rewriting
occurs.
It is in InitPlan, the same place we check to make sure that we are not
changing a sequence or a toast table. (actually initResultRelInfo called from
InitPlan). I gathered from the backend flowchart that this wasn't called
until all rewriting was done. Was I wrong?
If all rewriting _is_ done at that point, why is the view still in the
ResultRelInfo ?
--
Mark Hollomon
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: mhh@mindspring.com, tgl@sss.pgh.pa.us, jburton@scw.org, pgsql-hackers@postgresql.org
Subject: Re: [SQL] Rules with Conditions: Bug, or Misunderstanding
In-Reply-To: <00113022072200.00743@jupiter.hollomon.fam>
References: <3A255246.21430.688927F3@localhost> <19579.975544973@sss.pgh.pa.us> <00113022072200.00743@jupiter.hollomon.fam>
* 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