Olivier Dony 44b019bf76 [FIX] orm.browse_record: fields prefetching should ignore m2o pointing to models not loaded yet ...

This situation can occur due to custom fields (x_...) that are creating shortcuts between
objects without respecting the module dependencies. For example a custom m2o fields 
connecting a partner and a product would fail to be loaded at server startup when only
base is loaded, because product.product is not yet available.
This can usually be simply ignored, as the prefetching is just an optimization.
The custom fields should never be accessed during startup (e.g not function field
should use them), so that should never cause any issue.

bzr revid: odo@openerp.com-20110216142128-a9f4um5ky8cetl38

2011-02-16 15:21:28 +01:00

..

__init__.py

Changed encoding to coding ref: PEP: 0263

2009-10-20 16:22:23 +05:30

expression.py

expression: fix function.search() when it does not restrict

2011-01-17 10:41:08 +02:00

fields.py

[REVERT] fields: revert previous fix, until tests and addons are checked for compatibility

2011-02-01 14:07:21 +01:00

orm.py

[FIX] orm.browse_record: fields prefetching should ignore m2o pointing to models not loaded yet

2011-02-16 15:21:28 +01:00

osv.py

[FIX] osv: _constraints can be inherited by redefining a constraint with the same name

2011-01-17 10:47:50 +01:00

query.py

[IMP] osv.query,orm: removed trailing whitespace introduced by previous commits

2010-10-01 18:54:11 +02:00