Rakesh H S 906a0ed6fd Convergence: Fix concurrent update resource delete ... In convergence, wherein concurrent updates are possible, if a resource is deleted (by previous traversal) after dependency graph is created for new traversal, the resource remains in graph but wouldn't be available in DB for processing. It is prerequisite to have resources in DB before any action can be taken on them. Hence during convergence resource delete action, the resource entry from DB is not deleted i.e soft deleted, so that the latest/new update can find the entry. All of these soft deleted resources will be deleted when the stack has completed its operation. Closes-Bug: #1528560 Change-Id: I0b36ce098022560d7fe01623ce7b66d1d5b38d55		2016-07-05 12:27:37 +05:30
..
__init__.py	Add migration test framework	2013-12-20 12:32:58 +11:00
test_migrations.py	on-delete cascade rule for resource_data	2016-06-13 08:55:30 +00:00
test_sqlalchemy_api.py	Convergence: Fix concurrent update resource delete	2016-07-05 12:27:37 +05:30
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	Fixes migrate_data utils to avoid created_at filed	2015-04-01 15:28:33 +05:30