OCA
/
server-tools
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2327 Commits
13 Branches
0 Tags
45 MiB
Tree: 197a86d882
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '197a86d882'
${ noResults }
server-tools/test_onchange_helper/__manifest__.py

26 lines
891 B
Raw Normal View History

[IMP] onchange_helper: Improve performance when called on an existing record Before this change, the inmemory record was populated from values copied from the exisitng record. It was no predictable to know in advance which values were required to correctly play onchange methods. Therefore all the values defined on the model were copied from the exising record to populate the inmemory record. The side effect of this approach was that in a lot of cases, a lot of useless values was copied leading to performance issue with computed fields. With this change, we use the current record to call the onchange methods in an onchange context to avoid direct write to the database each time a new value is assigned by an onchange. At the end of the process, we restore the current record to its original state and return a dictionary with only the fields modified by the onchange.
6 years ago
​
​
​
​
​
​
​
test_onchange_helper 10.0.2.1.0
5 years ago
[IMP] onchange_helper: Improve performance when called on an existing record Before this change, the inmemory record was populated from values copied from the exisitng record. It was no predictable to know in advance which values were required to correctly play onchange methods. Therefore all the values defined on the model were copied from the exising record to populate the inmemory record. The side effect of this approach was that in a lot of cases, a lot of useless values was copied leading to performance issue with computed fields. With this change, we use the current record to call the onchange methods in an onchange context to avoid direct write to the database each time a new value is assigned by an onchange. At the end of the process, we restore the current record to its original state and return a dictionary with only the fields modified by the onchange.
6 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. # -*- coding: utf-8 -*-
  2. # Copyright 2019 ACSONE SA/NV
  3. # License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
  5. {
  6. "name": "Onchange Helper TEST",
  7. "summary": """
  8. Test addon for the onchange_helper addon""",
  9. "version": "10.0.2.1.0",
  10. "license": "AGPL-3",
  11. "author": "ACSONE SA/NV,Odoo Community Association (OCA)",
  12. "website": "https://acsone.eu/",
  13. "depends": ["onchange_helper"],
  14. "data": [
  15. 'security/test_onchange_helper_multi_line.xml',
  16. 'security/test_onchange_helper_multi.xml',
  17. "security/test_onchange_helper_emailmessage.xml",
  18. "security/test_onchange_helper_message.xml",
  19. "security/test_onchange_helper_discussion.xml",
  20. "security/test_onchange_helper_category.xml",
  21. ],
  22. "demo": [
  23. "demo/test_onchange_helper_discussion.xml",
  24. "demo/test_onchange_helper_message.xml",
  25. ]
  26. }