From: | Bartosz Dmytrak <bdmytrak(at)eranet(dot)pl> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: trigger node refresh error |
Date: | 2012-02-11 08:15:04 |
Message-ID: | CAD8_Uca+zcvrE6PYqWEXwss-dpF1-n54vNeoMRQcVQ_nHjmTKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Double checked on Mandriva Linux 2011 64bit pgAdmin 1.14.1
problem still exists.
You should use context menu on trigger node under the table. Even if
trigger function branch isn't extended then after extend You will find
duplicated nodes.
Reagards,
Bartek
2012/2/10 Guillaume Lelarge <guillaume(at)lelarge(dot)info>
> On Thu, 2012-02-09 at 14:47 +0100, bdmytrak(at)eranet(dot)pl wrote:
> > Hi,
> > I found strange GUI behaviour during enabling/disabling trigger.
> > When You disable trigger under the table node (trigger node is extended
> to prestent trigger function) then the trigger function node is duplicated,
> when You enable this trigger again (trigger node is still extended) then
> the trigger function node is duplicated again. This could continue over and
> over again until trigger node refresh.
> > When You refresh trigger node then "ghost" nodes dispire. All these
> nodes work as normal node (e.g. present SQL definition of trigger function,
> double click for details works, etc.).
> > Please take a look at screen shot (trigger has the same name as trigger
> function - this is intended)
>
> I tried on 1.14, and I don't have this issue.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www.dalibo.com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2012-02-11 12:16:48 | Re: problem using pgAdmin III |
Previous Message | James Ib Akoma | 2012-02-11 00:22:49 | problem using pgAdmin III |