Message-ID: <4047C4F3.4000608@Yahoo.com>
Date: Thu, 04 Mar 2004 19:08:19 -0500
From: Jan Wieck <JanWieck@Yahoo.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Fabien COELHO <coelho@cri.ensmp.fr>,
	PostgreSQL Patches <pgsql-patches@postgresql.org>
Subject: Re: "ALSO" keyword to "CREATE RULE" patch
References: <200403042331.i24NVs913028@candle.pha.pa.us>
In-Reply-To: <200403042331.i24NVs913028@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:

> Jan Wieck wrote:
>> Tom Lane wrote:
>> 
>> > Fabien COELHO <coelho@cri.ensmp.fr> writes:
>> >> Most of the patch deals with the documentation, which is rather ugly
>> >> because it keeps telling about "INSTEAD" vs "non-INSTEAD" rules, as there
>> >> is no name for the default behavior. I think "ALSO" fixes this issue as it
>> >> clarifies the explanations.
>> > 
>> > Hmm ... I find that argument much more convincing than any of the others
>> > ...
>> > 
>> > Jan, what do you think?  You invented this command's syntax IIRC.
>> 
>> I did not. We inherited it from Postgres 4.2. If people think an ALSO 
>> keyword will clearify things, what about renaming the whole CREATE RULE 
>> into something along the line CREATE QUERY REWRITE MACRO?
> 
> Are you saying you don't want ALSO added?
> 

No, I am saying that CREATE RULE is so often misinterpreted to work like 
a trigger and when we explain that it is more like Macro expansion 
before the query is executed they understand better. CREATE RULE itself 
is just vague, with or without ALSO.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #