Odoo/odoo/addons/test_new_api/models.py, branch 14.0

[IMP] base/test_*: Adapt tests to work with/without demo data

2019-11-05T12:08:02+00:00

[FIX] fields: 'bin_size' must have no effect on arbitrary binary field values

2019-10-22T12:25:52+00:00

This fixes a regression introduced by 291a0e99d137142bd24addd1054c1357ddd7125a.

closes odoo/odoo#39178

X-original-commit: 852ee32e3419c210a3844b0f943af8dd2bbdae88
Signed-off-by: Raphael Collet (rco)

[FIX] models: filtered_domain on date/datetime fields

2019-10-21T09:08:47+00:00

X-original-commit: 5399c139b884f721b92477533eae1e03bf4cf62b

[FIX] fields: ensure Binary are never recomputed with "bin_size"

2019-10-21T09:08:10+00:00

The compute methods are always expecting the real value and not the bin_size.

The solution is to always compute with `bin_size=False`, and then manually
compute the `bin_size` and set it on the cache of `bin_size=True`.

PR: #38292

Co-authored-by Sébastien Theys 

X-original-commit: 7744886d6141ca7971d91807d0444c707e10fdf8

[FIX] base: don't crash during CRUD if record does not exist

2019-10-15T14:33:07+00:00

- Let a model M define a Many2oneReference field F1.
- Let a model N define a One2many field F2 whose inverse is M->F1
- Define a computed field N->F3 that depends on N->F2

If, for whatever reason, a recordset of M contains records that have
been unlinked already and we try to unlink them again, the system will
crash with a MissingException error.

This happened because, while most _modified_trigger cases cover the case
of a MissingException (i.e. record not in cache), the case for a
Many2oneReference didn't.

This is fixed by simply ignoring these "stale" records in the
_modified_triggers section for Many2oneReference fields.

closes odoo/odoo#38816

X-original-commit: f3b05032f0576befda4dca870718afd429c21b0f
Signed-off-by: Adrian Torres (adt) 
Co-authored-by: mreficent

[FIX] models: consider all inactive records in modified()

2019-10-03T09:44:48+00:00

closes odoo/odoo#37863

Signed-off-by: Raphael Collet (rco)

[FIX] models, fields: cache consistency for one2many fields

2019-09-30T15:42:36+00:00

Issue: after many2one updates, the cache of the corresponding one2many
fields was inconsistent when the latter depends on `active_test`.  One
of the values in cache was updated, while the other was left intact.

We simplify the cache by not making the field depend on context: the
cache value contains all the records in the relation (corresponding to
`active_test=False`).  The value of the field is automatically filtered
by the `active` field when the value is accessed.

This makes it easier to maintain the cache value, guarantees its
consistency, and avoids queries to read the one2many field with
`active_test=False`, after having set it with `active_test=True`.

[FIX] *: add missing model description

2019-09-24T07:33:09+00:00

Some models did not specified a _description

[FIX] fields: default to ondelete='cascade' for required m2o fields on transient

2019-09-20T12:23:09+00:00

TransientModel (wizards) can be annoying because if they have required
many2one fields, those fields will default to `ondelete='restrict'`,
preventing user to delete the comodel records without deleting the
transient model records first.

To improve such case, we default to `ondelete='cascade'` for required
many2one field on a TransientModel (unless specified otherwise)

closes odoo/odoo#36738

Signed-off-by: Raphael Collet (rco)

[FIX] fields: clash with automatic fields and inheritance

2019-09-10T13:29:15+00:00

Consider a model M that defines `display_name` as a computed stored
field, then an extension of M that introduces a mixin model A before
that definition in the MRO of M's class.  The model A is expected to
have an automatic, non stored field `display_name`, while M must have
its non-automatic, stored field `display_name`.

closes odoo/odoo#36427

Signed-off-by: Raphael Collet (rco)