Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules - Mailing list pgsql-hackers

From Tom Lane
Subject Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules
Date
Msg-id 16542.1403012773@sss.pgh.pa.us
Whole thread Raw
In response to Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-06-17 11:22:17 +0200, Vik Fearing wrote:
>> On 06/17/2014 09:43 AM, Hannu Krosing wrote:
>>> Was'nt there a plan (consensus?) about deprecating rules altogether ?

>> I believe that was just for user access to them, ie CREATE RULE.  I
>> don't think there was ever question of purging them from the code base.

> I don't think any such concensus has been made? I wish it were, but the
> last discussions about it imo ended quite differently.

Yeah, I don't think there's any prospect of removing them in the near
future.  We'd need a (better-designed) replacement feature first.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: How to implement the skip errors for copy from ?
Next
From: Andres Freund
Date:
Subject: Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules