heat/heat/db/sqlalchemy
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
..
migrate_repo on-delete cascade rule for resource_data 2016-06-13 08:55:30 +00:00
__init__.py Stub out the database access API 2012-03-29 18:02:16 +02:00
api.py Convergence: Fix concurrent update resource delete 2016-07-05 12:27:37 +05:30
filters.py replace dict.iteritems() with six.iteritems(dict) 2014-08-06 10:56:09 +08:00
migration.py Squash database patches 2016-04-09 02:16:38 +00:00
models.py on-delete cascade rule for resource_data 2016-06-13 08:55:30 +00:00
types.py Remove usage of sqlalchemy mutables 2015-06-26 11:02:03 +02:00
utils.py Add retries to avoid dberror for user_creds_delete 2016-03-17 23:02:57 +05:30