DBManager: Don't test connection on start

This gives the individual services more freedom in how to handle
a failing connection.
pull/119/head
Mike Lang 5 years ago
parent 095e391b60
commit fc791e03d4

@ -19,8 +19,7 @@ class DBManager(object):
returning them. returning them.
It has the ability to serve as a primitive connection pool, as getting a It has the ability to serve as a primitive connection pool, as getting a
new conn will return existing conns it knows about first, but this mainly new conn will return existing conns it knows about first, but you
just exists to re-use the initial conn used to test the connection, and you
should use a real conn pool for any non-trivial use. should use a real conn pool for any non-trivial use.
Returned conns are set to seralizable isolation level, autocommit, and use Returned conns are set to seralizable isolation level, autocommit, and use
@ -30,9 +29,6 @@ class DBManager(object):
self.conns = [] self.conns = []
self.connect_timeout = connect_timeout self.connect_timeout = connect_timeout
self.connect_kwargs = connect_kwargs self.connect_kwargs = connect_kwargs
# get a connection to test whether connection is working.
conn = self.get_conn()
self.put_conn(conn)
def put_conn(self, conn): def put_conn(self, conn):
self.conns.append(conn) self.conns.append(conn)

Loading…
Cancel
Save