| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Command Triggers, patch v11 |
| Date: | 2012-03-03 00:12:46 |
| Message-ID: | CA+TgmoZkgpzFkw2odrog1r6x2Wwqwk+mQizbFR6zoQbTk6BArQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 28, 2012 at 10:09 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This seems over-complicated. Triggers on tables do not have
>> alterable properties, why should command triggers? I vote for
>>
>> CREATE COMMAND TRIGGER name ... properties ...;
>>
>> DROP COMMAND TRIGGER name;
>>
>> full stop. If you want to run the same trigger function on some
>> more commands, add another trigger name.
>
> +1
+1. I suggested the same thing a while back.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | anarazel@anarazel.de | 2012-03-03 00:39:13 | Re: Command Triggers, patch v11 |
| Previous Message | Thom Brown | 2012-03-03 00:08:33 | Re: Command Triggers, patch v11 |