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
..
psycopg2	Handling the bad/lost connection of a database server.	2016-08-29 12:01:35 +05:30
__init__.py	Code tidy.	2016-06-21 14:21:06 +01:00
abstract.py	Optimise Python imports.	2016-06-21 14:12:14 +01:00
registry.py	Stop using deprecated imports.	2016-07-22 16:25:23 +01:00