From e181f592f33b2ae382569927537aed84689ee44f Mon Sep 17 00:00:00 2001 From: Raphael Collet Date: Thu, 22 Nov 2018 11:00:53 +0000 Subject: [PATCH] [FIX] odoo: ormcache invalidation on loading registry Do not propagate cache invalidations to other workers when simply loading the registry. Only do it when installing/upgrading/uninstalling modules. --- odoo/modules/loading.py | 5 ----- 1 file changed, 5 deletions(-) diff --git a/odoo/modules/loading.py b/odoo/modules/loading.py index bc95e1c461d..5fb56887948 100644 --- a/odoo/modules/loading.py +++ b/odoo/modules/loading.py @@ -151,8 +151,6 @@ def load_module_graph(cr, graph, status=None, perform_checks=True, module_count = len(graph) _logger.info('loading %d modules...', module_count) - registry.clear_caches() - # register, instantiate and initialize models for each modules t0 = time.time() t0_sql = odoo.sql_db.sql_counter @@ -278,9 +276,6 @@ def load_module_graph(cr, graph, status=None, perform_checks=True, _logger.log(25, "%s modules loaded in %.2fs, %s queries", len(graph), time.time() - t0, odoo.sql_db.sql_counter - t0_sql) - registry.clear_caches() - - return loaded_modules, processed_modules def _check_module_names(cr, module_names):