Re: Deprecating RULES

On 11 October 2012 20:50, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> Not many RULE-lovers out there, once you've tried to use them.
>> Allowing RULEs complicates various things and can make security more difficult.
>
>> For 9.3, I suggest we create a DDL trigger by default which prevents
>> RULEs and throws an ERROR that explains they are now deprecated.
>
> This is utter nonsense. We can't deprecate them until we have a
> substitute that is better.

We do, they're called views and triggers, both of which are SQL Standard.

> If you want to get rid of rules, build the
> replacement; don't just try to be a pain in the ass to users.

Supporting broken and non-standard features *is* a pain in the ass to
users, since they are sometimes persuaded to use them and then regret
it. Or if they do, hit later problems.

You recently rejected a partitioning related patch because it used rules...

Anyway, lets start with a discussion of what rules give us that SQL
standard features do not?

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services