pgadmin4/web/pgadmin/misc
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
..
bgprocess Flask-Babel 0.11+ compatibility. Fixes #1496 2016-07-25 17:23:10 +01:00
depends Handling the bad/lost connection of a database server. 2016-08-29 12:01:35 +05:30
file_manager String fix. 2016-08-17 15:10:33 +01:00
sql Handling the bad/lost connection of a database server. 2016-08-29 12:01:35 +05:30
static/explain Integrate the graphical explain module in the Query Editor. 2016-05-16 01:07:54 +05:30
statistics Handling the bad/lost connection of a database server. 2016-08-29 12:01:35 +05:30
templates Get rid of canvas colouring in graphical explain. 2016-06-17 16:34:03 +01:00
__init__.py Stop using deprecated imports. 2016-07-22 16:25:23 +01:00