| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | "bdmytrak(at)eranet(dot)pl" <bdmytrak(at)eranet(dot)pl> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: trigger node refresh error |
| Date: | 2012-02-09 23:15:48 |
| Message-ID: | 1328829348.2155.3.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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 | Colin Beckingham | 2012-02-10 11:05:18 | Dev 1.15 Database Designer |
| Previous Message | Guillaume Lelarge | 2012-02-09 23:14:15 | Re: Feedback on database designer (1.15 Dev) |