Thread: trigger node refresh error
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)
pgAdmin 1.14.1 Win7 32bit
Regards,
Bartek
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)
pgAdmin 1.14.1 Win7 32bit
Regards,
Bartek
Attachment
On Thu, 2012-02-09 at 14:47 +0100, bdmytrak@eranet.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 triggerfunction node is duplicated, when You enable this trigger again (trigger node is still extended) then the triggerfunction 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 definitionof 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
On Fri, Feb 10, 2012 at 3:15 AM, Guillaume Lelarge <guillaume@lelarge.info> wrote:
I tried on 1.14, and I don't have this issue.On Thu, 2012-02-09 at 14:47 +0100, bdmytrak@eranet.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)
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
Hi,
the same problem for me too, trigger function node is duplicated then disable/enable trigger.
PgAdmin 1.14.1, Windows XP SP3, 32bit.
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@lelarge.info>
I tried on 1.14, and I don't have this issue.On Thu, 2012-02-09 at 14:47 +0100, bdmytrak@eranet.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)
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
On Sat, 2012-02-11 at 09:15 +0100, Bartosz Dmytrak wrote: > 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. > My bad. I used the "Disable triggers" of the table's contextual menu. So, yes, I get it now. Working on a fix. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
On Sat, 2012-02-11 at 15:51 +0100, Guillaume Lelarge wrote: > On Sat, 2012-02-11 at 09:15 +0100, Bartosz Dmytrak wrote: > > 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. > > > > My bad. I used the "Disable triggers" of the table's contextual menu. > So, yes, I get it now. Working on a fix. > Fix pushed. Thanks for your report. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com