Re: [pgAdmin4][Patch]: RM #3629 debugger: debug button does notbecome active when arguments 0 (integer) or empty string/space (text) are used - Mailing list pgadmin-hackers

From Dave Page
Subject Re: [pgAdmin4][Patch]: RM #3629 debugger: debug button does notbecome active when arguments 0 (integer) or empty string/space (text) are used
Date
Msg-id CA+OCxow28dLsuZRhFE0rOW12E-b9H3tkw29_e8xaFECyb96rtQ@mail.gmail.com
Whole thread Raw
In response to [pgAdmin4][Patch]: RM #3629 debugger: debug button does not becomeactive when arguments 0 (integer) or empty string/space (text) are used  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
List pgadmin-hackers
Thanks, applied.

On Fri, Nov 2, 2018 at 9:13 AM Akshay Joshi <akshay.joshi@enterprisedb.com> wrote:
Hi Hackers, 

Attached is the patch to fix #3629 debugger: debug button does not become active when arguments 0 (integer) or empty string/space (text) are used.

Patch contains fix for one more issue "Can not debug with the default parameter value."

--
Akshay Joshi
Sr. Software Architect


Phone: +91 20-3058-9517
Mobile: +91 976-788-8246


--
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: Allow use of 0 (integer) and empty strings asparamet
Next
From: Ioseph Kim
Date:
Subject: CentOS 7.x pgadmin4 3.5 require psutil module