From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: "ALSO" keyword to "CREATE RULE" patch |
Date: | 2004-03-04 23:24:11 |
Message-ID: | 4047BA9B.3010302@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-patches |
Tom Lane wrote:
> Fabien COELHO <coelho(at)cri(dot)ensmp(dot)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?
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-04 23:31:54 | Re: "ALSO" keyword to "CREATE RULE" patch |
Previous Message | Robert Treat | 2004-03-04 15:59:56 | Re: [DOCS] Request temporary freeze of libpgtcl chapter in manual |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-04 23:31:54 | Re: "ALSO" keyword to "CREATE RULE" patch |
Previous Message | Tom Lane | 2004-03-04 21:24:46 | Re: Fix for log_executor_stats |