121b8e6800
This was due to secondary fields loaded from database in 'onchange' mode. In that mode, the secondary fields were marked 'dirty', and therefore returned by the method `onchange`. The fix consists in loading those secondary fields in cache before processing the onchanges. This incidentally fixes a test on method `onchange`: in a one2many field, some dirty fields were unexpectedly returned in the result. This was due to those fields being loaded while processing onchanges. |
||
|---|---|---|
| .. | ||
| base | ||
| test_access_rights | ||
| test_convert | ||
| test_converter | ||
| test_documentation_examples | ||
| test_exceptions | ||
| test_impex | ||
| test_inherit | ||
| test_limits | ||
| test_new_api | ||
| test_uninstall | ||
| test_workflow | ||
| __init__.py | ||