pgadmin4/web/pgadmin/browser
Ashesh Vashi f12d981a9d Handling the bad/lost connection of a database server.
Made backend changes for:
* Taking care of the connection status in the psycopg2 driver. And, when
  the connection is lost, it throws a exception with 503 http status
  message, and connection lost information in it.
* Allowing the flask application to propagate the exceptions even in the
  release mode.
* Utilising the existing password (while reconnection, if not
  disconnected explicitly).
* Introduced a new ajax response message 'service_unavailable' (http
  status code: 503), which suggests temporary service unavailable.

Client (front-end) changes:
* To handle the connection lost of a database server for different
  operations by generating proper events, and handle them properly.

Removed the connection status check code from different nodes, so that
- it generates the proper exception, when accessing the non-alive
  connection.

Fixes #1387
2016-08-29 12:01:35 +05:30
..
server_groups Handling the bad/lost connection of a database server. 2016-08-29 12:01:35 +05:30
static Fix renaming of constraints from the table dialogue. Fixes #1500 2016-08-03 15:39:14 +01:00
templates/browser Handling the bad/lost connection of a database server. 2016-08-29 12:01:35 +05:30
tests Test suite enhancements: 2016-08-09 16:05:40 +01:00
__init__.py Allow the user to configure tabs in the SQL editor. Fixes #1406 2016-08-19 11:40:19 +01:00
collection.py Handling the bad/lost connection of a database server. 2016-08-29 12:01:35 +05:30
utils.py Stop using deprecated imports. 2016-07-22 16:25:23 +01:00