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

This commit is contained in:
Akshay Joshi 2018-03-26 13:59:49 +01:00 committed by Dave Page
parent 413709fc78
commit 1baddd5e9a
2 changed files with 2 additions and 1 deletions

View File

@ -92,6 +92,7 @@ Bug fixes
| `Bug #3079 <https://redmine.postgresql.org/issues/3079>`_ - Fix handling of tie/datetime array types when adding columns to a table
| `Bug #3080 <https://redmine.postgresql.org/issues/3080>`_ - Fix alignment issues in keyboard shortcut options
| `Bug #3081 <https://redmine.postgresql.org/issues/3081>`_ - Add missing reverse-engineered SQL header and drop statement for sequences
| `Bug #3090 <https://redmine.postgresql.org/issues/3090>`_ - Ensure message severity is decoded when necessary by the driver
| `Bug #3094 <https://redmine.postgresql.org/issues/3094>`_ - Ensure all messages are retrieved from the server in the Query Tool
| `Bug #3099 <https://redmine.postgresql.org/issues/3099>`_ - Fix creation of tables and columns in GPDB
| `Bug #3105 <https://redmine.postgresql.org/issues/3105>`_ - Ensure we can properly update rows with upper-case primary key columns

View File

@ -1580,7 +1580,7 @@ Failed to reset the connection to the server due to following error:
if exception_obj.diag.severity is not None \
and exception_obj.diag.message_primary is not None:
ex_diag_message = u"{0}: {1}".format(
exception_obj.diag.severity,
self.decode_to_utf8(exception_obj.diag.severity),
self.decode_to_utf8(exception_obj.diag.message_primary)
)
# If both errors are different then only append it