Odoo/openerp/osv/fields.py, branch 14.0 The current checkout of upstream Odoo [REM] models: remove `_columns` 2016-08-31T15:21:53+00:00 Raphael Collet rco@openerp.com 2016-08-25T15:15:25+00:00 8ea5f493918f7cb0e9092124c59406d503b6d570 






[REM] openerp.osv.fields: remove old-style function fields
2016-08-31T15:21:48+00:00

Raphael Collet
rco@openerp.com

2016-08-22T09:33:46+00:00

2b587d34ff30147c03baf16e998effe46ce5d9cf












[REF] fields: implement sparse fields as computed fields
2016-08-31T15:21:47+00:00

Raphael Collet
rco@openerp.com

2016-08-19T15:41:33+00:00

0fc697a3f78dca4d6df1e8c73668242bc0467386












[REF] fields: implement company-dependent fields as computed fields
2016-08-31T15:21:47+00:00

Raphael Collet
rco@openerp.com

2016-08-04T12:38:10+00:00

b258f4b842f3ed34f09acb7541983e627744359e












[REM] models: remove `_all_columns`
2016-08-31T15:21:45+00:00

Raphael Collet
rco@openerp.com

2016-08-25T14:38:32+00:00

ff5e44d2dece70f2d1f56eba7dd4a5d2050c59ef












[IMP] tools: sanitizer: add and clean sanitize options
2016-08-30T13:54:56+00:00

Thibault Delavallée
tde@openerp.com

2016-08-19T11:49:48+00:00

02c748be59ac8abc44c945218587e7b8a8e06a28

Now having

 * sanitize: run the sanitizer to clean the html (removing javascripts,
   unwanted tags, ...)
 * sanitize_tags: only a subset of tags is allowed in html content.
   Unwelcomed tags are remove dand their content stripped.
 * sanitize_attributes: only a subset of attributes is allowed.
 * sanitize_style: only a subset of style attributes is allowed. Style
   attributes are parsed to keep only a white list.
 * strip_style: all style is removed. It bypasses sanitize_style as there
   is no need to sanitize something that is removed.
 * strip_classes: remove class attributes

Fields parameters have also been updated to match the sanitize options. Html
fields by default are sanitized with sanitize_tags activated but without any
further options. All addons have been updated to match the new options
according to their previous behavior.





Now having

 * sanitize: run the sanitizer to clean the html (removing javascripts,
   unwanted tags, ...)
 * sanitize_tags: only a subset of tags is allowed in html content.
   Unwelcomed tags are remove dand their content stripped.
 * sanitize_attributes: only a subset of attributes is allowed.
 * sanitize_style: only a subset of style attributes is allowed. Style
   attributes are parsed to keep only a white list.
 * strip_style: all style is removed. It bypasses sanitize_style as there
   is no need to sanitize something that is removed.
 * strip_classes: remove class attributes

Fields parameters have also been updated to match the sanitize options. Html
fields by default are sanitized with sanitize_tags activated but without any
further options. All addons have been updated to match the new options
according to their previous behavior.







[FIX] fields: do not serialize more digits than necessary in `monetary._symbol_set()`
2016-06-23T08:08:57+00:00

Raphael Collet
rco@openerp.com

2016-06-22T14:06:09+00:00

1ba91042d673cde921f9d47884866db6f9174b7d

Add a class for float objects that carry their precision digits, use it for the
value of monetary fields in record cache, and serialize them as expected for
the database.





Add a class for float objects that carry their precision digits, use it for the
value of monetary fields in record cache, and serialize them as expected for
the database.







[REM] fields: remove support for deprecated properties `read` and `write`
2016-06-16T14:50:46+00:00

Raphael Collet
rco@openerp.com

2016-05-30T07:59:39+00:00

684df5b2dc2d26e223e14f0704e20db6fa8f7ff6












[IMP] fields: do not group property fields with 'multi'
2016-05-25T08:08:24+00:00

Raphael Collet
rco@openerp.com

2016-05-24T11:45:03+00:00

25b584c0f371a64441a11954dd7d659501b19cc0

Reading N property fields is as costly as reading each field separately.
Reading them one by one makes more sense performance-wise, as you will only
read the ones you need.





Reading N property fields is as costly as reading each field separately.
Reading them one by one makes more sense performance-wise, as you will only
read the ones you need.







[FIX] fields: add property `auto_join` on many2many fields
2016-05-11T09:40:24+00:00

Raphael Collet
rco@openerp.com

2016-05-06T07:39:28+00:00

de54107fecfa5b177f35574639aa660c41ee2ebf

This makes this property available on all relational fields, although the
feature is currently not implemented on many2many fields.





This makes this property available on all relational fields, although the
feature is currently not implemented on many2many fields.