From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: [pgAdmin4][RM3554] Debugger scroll issue for long procedures |
Date: | 2018-08-27 13:14:25 |
Message-ID: | CAM9w-_=+q=YcXPEhfT_aeOrnJFu-oADiP7v0qxLcE8HUh4VTFA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Hackers,
Please hold on with the patch. As discussed and found by Ashesh Vashi, if
we <Step In> the function called recursively then it is loading the
debugger with source code again which can be avoided and will improve
performance if the function is large.
Will send the updated patch along with the required changes. Thank you
Ashesh.
On Mon, Aug 27, 2018 at 6:16 PM Aditya Toshniwal <
aditya(dot)toshniwal(at)enterprisedb(dot)com> wrote:
> Hi Hackers,
>
> Attached is the patch to make debugger scroll automatically to current
> active line and scroll along with StepIn/StepOut. Previously, we had to
> manually scroll.
>
> Kindly review.
>
> --
> Thanks and Regards,
> Aditya Toshniwal
> Software Engineer | EnterpriseDB Software Solutions | Pune
> "Don't Complain about Heat, Plant a tree"
>
--
Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"
From | Date | Subject | |
---|---|---|---|
Next Message | Akshay Joshi | 2018-08-27 13:41:32 | pgAdmin 4 commit: Ensure external table node should be visible only for |
Previous Message | Aditya Toshniwal | 2018-08-27 12:46:53 | [pgAdmin4][RM3554] Debugger scroll issue for long procedures |