Olivier Dony c87b9c6539 [FIX] decimal_precision: avoid refreshing float precisions at each cache invalidation ... 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.		2014-11-19 12:53:58 +01:00
..
i18n	[I18N] Update translations from Launchpad 8.0 branches	2014-10-08 17:52:25 +02:00
security	[FIX] decimal.precision: add access right for decimal_precision_test	2014-01-13 09:23:41 +01:00
tests	[IMP] use model._fields instead of model._all_columns to cover all fields	2014-11-04 13:47:57 +01:00
__init__.py	[FIX] replace from/import stuffs of openerp stuffs by from/import openerp.stuffs (2)	2012-12-17 16:58:19 +01:00
__openerp__.py	[IMP] emoving bad code, no invitation system on events	2012-09-26 14:16:27 +02:00
decimal_precision.py	[FIX] decimal_precision: avoid refreshing float precisions at each cache invalidation	2014-11-19 12:53:58 +01:00
decimal_precision_view.xml	Removed version="7.0" from form views	2014-06-12 09:09:59 +02:00