| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enabling/disabling triggers and rules |
| Date: | 2011-07-09 12:59:29 |
| Message-ID: | 1310216370.2101.37.camel@laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Sat, 2011-07-09 at 10:18 +0100, Dave Page wrote:
> 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.
>
Agreed.
> > 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.
>
Fixed. In 1.14 and master.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin Trac | 2011-07-09 13:20:30 | Re: [pgAdmin III] #5: Modifying an object's schema via the UI |
| Previous Message | Guillaume Lelarge | 2011-07-09 12:58:26 | pgAdmin III commit: Fix SQL query for enabled/disabled triggers and rul |