PATCH: To fix the issue in trigger node (pgAdmin4)

From: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: PATCH: To fix the issue in trigger node (pgAdmin4)
Date: 2016-11-18 10:55:31
Message-ID: CAKKotZTypa23-UNnxmwSWCSeJNQQmQqCZ=-+JV=8CsWnG7Yz3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

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

Attachment Content-Type Size
RM_1747.patch application/octet-stream 5.7 KB

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Khushboo Vashi 2016-11-18 11:23:40 [pgAdmin4][Patch]: RM #1855
Previous Message Dave Page 2016-11-18 10:55:03 pgAdmin 4 commit: Prevent users selecting elements of the UI that shoul