Renat Akhmerov afb0f584c5 Use "passive_deletes=True" in ORM relationships ... * Using "passive_deletes=True" when configuring relationships with SQLAlchemy significantly reduces memory footprint when deleting a graph of objects (e.g. root workflow execution with all dependent tasks, actions and sub workflows) from DB. This happens because in this case SQLAlchemy doesn't load those dependent objects that are not yet in the session and rather relies on cascading mechanisms of databases which are activated by the proper configuration of foreign key columns. For example, "ON DELETE CASCADE" clause in the foreign key definition in case of for MySQL. Particularly, this change reduces memory footprint of API processes when deleting large graphs of executions and execution expiration policy mechanism where the same happens but on the engine side. * Added a test to make sure that cascaded deletion works well with this new property. Related-Bug: #1757966 Change-Id: I36988817fb8e7695094ef98958b8aa151208fadb		2018-05-15 16:04:02 +07:00
..
__init__.py	Adding pecan, wsme, oslo and adjusting packages	2013-11-21 13:47:42 +07:00
launch.py	Use "passive_deletes=True" in ORM relationships	2018-05-15 16:04:02 +07:00