Olivier Dony 8874fb058f [FIX] module.loading: ensure installed modules are all loaded before installing new ones ... After the recent change to make module install atomically (code *and* data), we ran into issues when installing a new module indirectly triggers code of a not-yet-loaded-but-installed module, via its data that is already in the database (e.g. worflows or reports modified by this module within another module, that now refer to its code). To avoid this, we now make sure that we only install new modules on top of a consistent system (code *and* data), by loading all installed or 'to upgrade' modules *before* starting to install new ones. lp bug: https://launchpad.net/bugs/809168 fixed bzr revid: odo@openerp.com-20110712133343-unf610k23fa6d3pk		2011-07-12 15:33:43 +02:00
..
__init__.py	[REF] renamed modules.__init__ to modules.loading.	2011-05-11 19:48:41 +02:00
db.py	[REF] simplified init_db/load_modules:	2011-05-17 11:18:22 +02:00
graph.py	[REF] module code goes into openerp.modules.module.	2011-05-11 19:24:48 +02:00
loading.py	[FIX] module.loading: ensure installed modules are all loaded before installing new ones	2011-07-12 15:33:43 +02:00
migration.py	[REF] module code goes into openerp.modules.module.	2011-05-11 19:24:48 +02:00
module.py	[REF] orm: defer foreign key creation.	2011-06-10 16:05:21 +02:00
registry.py	[MERGE] orm: _auto_init made of smaller methods, use a metaclass to discover new models.	2011-06-15 18:01:23 +02:00