Zane Bitter 0abf43535d Don't use wrap_db_retry on subtransaction in resource_create_replacement() ... The wrap_db_retry decorator must be used outside the outermost DB transaction. Using it on a subtransaction means that the main transaction gets marked for rollback but not closed, leaving the session in the 'inactive' state. This change ensures that the decorator is not used when we update the previous resource from within a subtransaction as part of creating a replacement resource, and instead the retry happens outside the main transaction. Change-Id: I28bfcc43b108d4d907098b2f0cf3553aab399553 Task: 36957 (cherry picked from commit 2398191be9)		2019-10-18 15:30:01 +00:00
..
__init__.py	Add migration test framework	2013-12-20 12:32:58 +11:00
test_migrations.py	Remove db api and tables for CloudWatch	2018-01-28 09:35:07 +05:30
test_sqlalchemy_api.py	Don't use wrap_db_retry on subtransaction in resource_create_replacement()	2019-10-18 15:30:01 +00:00
test_sqlalchemy_filters.py	Re-factor db sqlalchemy tests	2015-03-31 11:41:40 -04:00
test_sqlalchemy_types.py	Re-factor db sqlalchemy tests	2015-03-31 11:41:40 -04:00
test_utils.py	Remove unnecessary setUp and tearDown	2016-09-30 10:56:31 +08:00