Re: Enabling/disabling triggers and rules - Mailing list pgadmin-hackers

From Dave Page
Subject Re: Enabling/disabling triggers and rules
Date
Msg-id CA+OCxozFE6L9HqpZjcHjt9VAvxbmu2CRkY4eRfx92AdkkKPEXA@mail.gmail.com
Whole thread Raw
In response to Enabling/disabling triggers and rules  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: Enabling/disabling triggers and rules  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgadmin-hackers
On Sat, Jul 9, 2011 at 10:12 AM, Guillaume Lelarge
<guillaume@lelarge.info> wrote:
> Hi,
>
> Right now, the enabled/disabled state of a trigger and a rule is not
> displayed in the SQL pane of the browser. I can understand we don't
> display its state if the object is enabled, but shouldn't we display
> that the object is disabled in the SQL pane if it is? Just like we show
> a FK is invalid when it is.
>
> Any opinions on that issue?

We should include the SQL to disable it, yes. That is required to
recreate the object to the same state.

> Oh, and do we consider this a bug (so to be fixed in 1.14), or a new
> feature?

I'd call that a bug.


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgadmin-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: pgAdmin III commit: Make sure the SQL pane is updated when validating a
Next
From: Thom Brown
Date:
Subject: Re: [FEATURE] Add schema option to all relevant objects