oslo.db/oslo_db
Mike Bayer 7c5b7d3e03 Don't access connection.info if connection is invalidated
The connection.info dictionary comes from the underlying
pooled connection, which in a disconnection situation
is not there; trying to access it makes it try to reconnect.
Inside of rollback(), SQLAlchemy doesn't allow us to
reconnect yet because we haven't finished removing the
transctional state that corresponds to the now-discarded
connection.  Therefore we have to check connection.invalidated
inside of our rollback handlers before trying to add/remove tokens
from connection.info.

Change-Id: Icd10ada68d6d53410ac88eca3577f04c5e30087e
Resolves-bug: #1704474
2017-07-14 16:15:01 -04:00
..
locale Imported Translations from Zanata 2017-03-24 07:13:44 +00:00
sqlalchemy Don't access connection.info if connection is invalidated 2017-07-14 16:15:01 -04:00
tests Don't access connection.info if connection is invalidated 2017-07-14 16:15:01 -04:00
__init__.py Move files out of the namespace package 2014-12-24 13:28:48 +02:00
_i18n.py Remove log translations 2017-03-30 08:42:42 +08:00
api.py Remove log translations 2017-03-30 08:42:42 +08:00
concurrency.py Remove log translations 2017-03-30 08:42:42 +08:00
exception.py Enable MySQL Storage Engine selection 2017-06-26 10:33:01 -06:00
options.py Enable MySQL Storage Engine selection 2017-06-26 10:33:01 -06:00