| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Indicate disabled triggers in \d |
| Date: | 2006-11-06 14:12:32 |
| Message-ID: | 454F42D0.8070009@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> "Brendan Jurd" <direvus(at)gmail(dot)com> writes:
>
>> My first impulse was to just append a " (disabled)" after each
>> disabled trigger, but perhaps that is not visually obvious enough,
>> especially if the table has many triggers on it.
>>
>
> Agreed, but maybe put it up at the front?
>
> Triggers:
> y AFTER DELETE ON x FOR EACH ROW EXECUTE PROCEDURE do_something()
> z (disabled) BEFORE INSERT ON x FOR EACH ROW EXECUTE PROCEDURE input_stuff()
>
>
>
+1. This bit me recently. Or maybe, in the interests of preserving
screen space, a [*] for enabled and [x] for disabled, or something similar.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-06 15:49:42 | Re: Is python 2.5 supported? |
| Previous Message | Dr. Ernst Molitor | 2006-11-06 10:35:52 | Re: WITH SYSID dropped |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2006-11-06 23:44:06 | Re: Indicate disabled triggers in \d |
| Previous Message | Simon Riggs | 2006-11-06 08:25:53 | Re: [HACKERS] Bug in WAL backup documentation |