Had to alter marketing_campaign as it imported get_precision from deeper into the module instead of properly getting it from the module's toplevel.
- Preserved explicit 3rd-party copyright notices - Explicit boilerplate should not be necessary - copyright law applies automatically in all countries thanks to Berne Convention + WTO rules, and a reference to the applicable license is clear enough.
The patch speeds up the cache invalidation in the registry, and make most models use the generic method `clear_caches` instead of specific `clear_cache` methods.
This fixes a bug on some methods. Because `ormcache` uses the decorator `decorator`, the `context` argument is passed positionally to the decorated lookup method, instead of being passed as a keyword argument. As a consequence, the context dictionary is included in the cache key, which makes the cache lookup fail all the time. Using the new API of `ormcache` gracefully fixes this issue.
The computed value of parameter digits is no longer stored into fields and columns; instead the value is recomputed everytime it is needed. Note that performance is not an issue, since the method `get_precision` of model 'decimal.precision' is cached by the orm. This simplifies the management of digits on fields and saves about 300Kb per registry.
Let 2015 be a year without modelines! cf #4174
Changing the decimal precision of float fields is a rare operation, while cache clearing occurs fairly frequently. Signaling a full registry change when the decimal precision is changed (instead of a mere cache change) is therefore a better trade-off, and more semantically correct as well. This way we avoid the decimal precision refresh for each invalidation. Registry invalidation implies cache invalidation.
The old-api model._all_columns contains information about model._columns and inherited columns. This dictionary is missing new-api computed non-stored fields, and the new field objects provide a more readable api... This commit contains the following changes: - adapt several methods of BaseModel to use fields instead of columns and _all_columns - copy all semantic-free attributes of related fields from their source - add attribute 'group_operator' on integer and float fields - base, base_action_rule, crm, edi, hr, mail, mass_mailing, pad, payment_acquirer, share, website, website_crm, website_mail: simply use _fields instead of _all_columns - base, decimal_precision, website: adapt qweb rendering methods to use fields instead of columns
When a decimal_precision record is created/modified, the float fields of the models in the registry must be reset. This was done on old-API columns only. It is now handled by the new-API fields.