Re: Rules: A Modest Proposal

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rules: A Modest Proposal
Date: 2009-10-07 19:55:40
Message-ID: 87y6nn5683.fsf@dba2.int.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

sfrost(at)snowman(dot)net (Stephen Frost) writes:

> * David Fetter (david(at)fetter(dot)org) wrote:
>> On Sun, Oct 04, 2009 at 04:07:40PM -0400, Robert Haas wrote:
>> > > The radical proposal was the RULE system.  It's been tested now,
>> > > and it's pretty much failed.
>> >
>> > You still haven't explained what actual benefit we'd get out of
>> > doing this.
>>
>> Removing land mines is a benefit.
>
> Removing useful functionality without replacing it is definitely worse.

Well, I think we can start here with the premise that there is
disagreement on this...

Position #1:
Rules are "land mines"; in effect, an "anti-feature."

Position #2:
Rules represent "useful functionality."

I'd tend more towards #1, myself, and with that as a premise,
replacement isn't, per se, necessary.

The one and only rule I have in the sizable app I'm working on is
there because of the absence of updatable views.

If we could put triggers on views, then I wouldn't need the rule, and
that seems like a reasonable "use case" to have drawn into the modest
proposal...
--
select 'cbbrowne' || '@' || 'gmail.com';
http://linuxdatabases.info/info/emacs.html
"I really only meant to point out how nice InterOp was for someone who
doesn't have the weight of the Pentagon behind him. I really don't
imagine that the Air Force will ever be able to operate like a small,
competitive enterprise like GM or IBM." -- Kent England

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-10-07 20:58:18 Re: Issues for named/mixed function notation patch
Previous Message Michael Renner 2009-10-07 19:09:40 Performance testing framework..