| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Daniel Farina <daniel(at)heroku(dot)com>, darren(at)darrenduncan(dot)net, Peter Geoghegan <peter(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deprecating RULES |
| Date: | 2012-10-17 17:02:29 |
| Message-ID: | 507EE4A5.4080307@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/17/2012 02:48 AM, Simon Riggs wrote:
> Would you or someone else be able to come up with some words of
> caution for us to put in the manual that would be helpful to
> developers?
>
> There isn't even a list of caveats for rules.
I think we need the inverse. Some documentation on why to use rules and
this basically boils down to the problem. Can anyone tell me a reason to
use explicit rules over a trigger and function combination?
And that is the crux of the issue. If we can't identify a reason the
feature currently exists and we have a suitable and better replacement,
the feature should be deprecated and removed.
My suggestion for docs is:
Note: Do not use, use Triggers with Functions instead <link>
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC
@cmdpromptinc - 509-416-6579
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-10-17 17:12:47 | Re: Deprecating RULES |
| Previous Message | Alvaro Herrera | 2012-10-17 16:10:37 | Re: embedded list |