Re: PATCH: To fix the issue in trigger node (pgAdmin4) - Mailing list pgadmin-hackers

From Dave Page
Subject Re: PATCH: To fix the issue in trigger node (pgAdmin4)
Date
Msg-id CA+OCxoy7xXienDRzEUh3oR4k4uhmE2YCEZSuX_05Xw9kc2FRAw@mail.gmail.com
Whole thread Raw
In response to PATCH: To fix the issue in trigger node (pgAdmin4)  (Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com>)
List pgadmin-hackers
Thanks, applied.

On Fri, Nov 18, 2016 at 10:55 AM, Murtuza Zabuawala
<murtuza.zabuawala@enterprisedb.com> wrote:
> Hi,
>
> PFA patch to to fix the issue where trigger node was not gets added in
> browser tree after creation & also refresh on specific trigger node was not
> working.
> RM#1747
>
> I found the similar issue on Index node, Refresh on specific index node was
> not working, fix is included in the patch for the same.
>
> Issue:
> Wrong parent id was given while creation of trigger & node() method was not
> implemented which was causing refresh error issue.
>
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>



--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgadmin-hackers by date:

Previous
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Add newly created triggers to the treeview. Fixes #17
Next
From: Dave Page
Date:
Subject: pgAdmin 4 commit: Ensure dialogue panels show their errors themselves,