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
..
sqlalchemy	Don't access connection.info if connection is invalidated	2017-07-14 16:15:01 -04:00
__init__.py	Test that concurrent sqlalchemy transactions don't block	2015-07-16 20:20:45 +10:00
base.py	Move files out of the namespace package	2014-12-24 13:28:48 +02:00
test_api.py	api: use sane default in wrap_db_retry()	2016-06-29 13:38:02 +02:00
test_concurrency.py	Fix parameters of assertEqual are misplaced	2016-07-20 18:11:34 +08:00
utils.py	Update Oslo imports to remove namespace package	2015-01-21 18:23:56 -05:00