Re: Indicate disabled triggers in \d

From: David Fetter <david(at)fetter(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Indicate disabled triggers in \d
Date: 2006-11-06 23:44:06
Message-ID: 20061106234406.GC31260@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Mon, Nov 06, 2006 at 09:12:32AM -0500, Andrew Dunstan wrote:
> 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.

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

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

Remember to vote!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Luke Lonergan 2006-11-06 23:46:01 Re: Introducing an advanced Frequent Update
Previous Message Andrew 2006-11-06 23:35:57 Direct Client Req from ProV-----PostGre Database Developer at San Diego, CA

Browse pgsql-patches by date

  From Date Subject
Next Message Brendan Jurd 2006-11-07 04:55:11 Re: [HACKERS] Indicate disabled triggers in \d
Previous Message Andrew Dunstan 2006-11-06 14:12:32 Re: Indicate disabled triggers in \d