diff options
| author | Raphael Collet <rco@openerp.com> | 2015-05-06 14:37:56 +0200 |
|---|---|---|
| committer | Raphael Collet <rco@openerp.com> | 2015-05-06 15:24:39 +0200 |
| commit | 1a535b9d870ced75d9b561bd0bb634c87b1fa999 (patch) | |
| tree | e9042811ed2a4dfab4c42635befd7cea64e93200 /addons/analytic_user_function/analytic_user_function_view.xml | |
| parent | 6b72008c32345e1413f654ba24d0b521dc9bdf33 (diff) | |
[IMP] models: in recompute, do not store fields that should not be recomputed
Consider a new field that uses the same compute method as another existing
field. When the field is introduced in database, its value must be computed on
existing records. In such a case, the existing field should not be written, as
its value is not supposed to have changed. Not writing on the existing field
can avoid useless recomputations in cascade, which is the reason we introduce
this patch.
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function_view.xml')
0 files changed, 0 insertions, 0 deletions