pgAdmin 4 commit: Handle composite type return values properly in the d

From: Dave Page <dpage(at)pgadmin(dot)org>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: pgAdmin 4 commit: Handle composite type return values properly in the d
Date: 2016-09-20 10:27:55
Message-ID: E1bmIHL-0006bI-1q@gothos.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Handle composite type return values properly in the debugger. Fixes #1662

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=f991354f9a17a04b6530b460880936f51023ece7
Author: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>

Modified Files
--------------
web/pgadmin/tools/debugger/__init__.py | 19 ++++++++------
.../tools/debugger/templates/debugger/js/direct.js | 29 +++++++++++-----------
2 files changed, 27 insertions(+), 21 deletions(-)

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2016-09-20 10:28:09 Re: PATCH: To fix the issue displaying composite result types in debugger (pgAdmin4)
Previous Message Dave Page 2016-09-20 10:18:31 Re: [pgAdmin4][Patch]: RM1627 - Objects are not visible after creation until press refresh button