Re: Indicate disabled triggers in \d - Mailing list pgsql-hackers

From David Fetter
Subject Re: Indicate disabled triggers in \d
Date
Msg-id 20061106234406.GC31260@fetter.org
Whole thread Raw
In response to Re: Indicate disabled triggers in \d  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Indicate disabled triggers in \d  ("Brendan Jurd" <direvus@gmail.com>)
List pgsql-hackers
On Mon, Nov 06, 2006 at 09:12:32AM -0500, Andrew Dunstan wrote:
> Tom Lane wrote:
> >"Brendan Jurd" <direvus@gmail.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.

For this case, I think clarity is more important than saving screen
space.

Cheers,
D
-- 
David Fetter <david@fetter.org> http://fetter.org/
phone: +1 415 235 3778        AIM: dfetter666                             Skype: davidfetter

Remember to vote!


pgsql-hackers by date:

Previous
From: "Andrew"
Date:
Subject: Direct Client Req from ProV-----PostGre Database Developer at San Diego, CA
Next
From: "Luke Lonergan"
Date:
Subject: Re: Introducing an advanced Frequent Update