From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Enabling/disabling triggers and rules |
Date: | 2011-07-09 09:18:48 |
Message-ID: | CA+OCxozFE6L9HqpZjcHjt9VAvxbmu2CRkY4eRfx92AdkkKPEXA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Sat, Jul 9, 2011 at 10:12 AM, Guillaume Lelarge
<guillaume(at)lelarge(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-07-09 09:33:19 | Re: [FEATURE] Add schema option to all relevant objects |
Previous Message | Guillaume Lelarge | 2011-07-09 09:14:27 | pgAdmin III commit: Make sure the SQL pane is updated when validating a |