diff options
| author | Denis Ledoux <dle@odoo.com> | 2015-12-22 16:12:56 +0100 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2015-12-22 16:22:13 +0100 |
| commit | f3ef7001cf35da72a6c35d958b3360fc9b2dd26d (patch) | |
| tree | 5691cd76987a189c28a5ecc48c527d0d1d5e6f99 /addons/web/static/src | |
| parent | 1057542f9f74b184a6a9c6b33357a60ccd721bb5 (diff) | |
[FIX] account: prevent recomputation of related field `internal_type`
When creating a new `account.account`,
or writing on an existing one, changing the
`type`, the source of the related field
`internal_type`, `user_type_id.type`, was
re-written (re-stored) because the field
was not read-only.
In addition, the re-store of the value
of this field triggered the re-store of the related
field `internal_type` on all other `account.account`
records using this `internal_type`, which leaded to:
- Performance issues
- Potential access rights issues, if this leaded
to write operations on records to which the user
does not have the access (multi-company rules, among others)
Forcing the field as read-only allow to not pass the value of this
`internal_type` from the web client to the server when
creating or editing an `account.account`.
Besides, the field is required in the view, to correctly trigger
the according onchange method:
```
@api.onchange('internal_type')
def onchange_internal_type(self):
```
opw-660292
Closes #10143
Diffstat (limited to 'addons/web/static/src')
0 files changed, 0 insertions, 0 deletions
