pgAdmin 4 commit: Decode the severity field in database exception objec

From: Dave Page <dpage(at)pgadmin(dot)org>
To: pgadmin-hackers(at)postgresql(dot)org
Subject: pgAdmin 4 commit: Decode the severity field in database exception objec
Date: 2018-03-26 12:59:52
Message-ID: E1f0Rj6-00066n-Qn@gothos.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Decode the severity field in database exception objects properly. Fixes #3090

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgadmin4.git;a=commitdiff;h=1baddd5e9a8d66daefa4c9e1b6a6ba10ba1130ea
Author: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>

Modified Files
--------------
docs/en_US/release_notes_3_0.rst | 1 +
web/pgadmin/utils/driver/psycopg2/connection.py | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2018-03-26 13:00:00 Re: [pgAdmin4][patch]: RM #3090 pgadmin shows misleading "Query returned successfully" with incorrect SQL
Previous Message Dave Page 2018-03-26 12:37:56 Re: [pgAdmin4][Patch]: RM #1978 - Add an option to allow user to disable alertifyjs and acitree animations