3 people b415533dca [REF] crm(_iap_lead): use read_group instead of computing len of one2many fields ...

PURPOSE

Several counter fields are performed inefficiently. They use compute methods
using length of 2many fields instead of making use of more efficient ORM
methods like read_group.

SPECIFICATIONS

No functional change, only technical performance improvements.

Purpose is to improve lead_count performance. Some people claim to gain a lot
of queries: from 90 to 30 SQL queries to read 39 partners. Hard to reproduce.

LINKS

Task ID 2196182
PR odoo/odoo#44662

Co-Authored-By: Fabien Pinckaers <fp@odoo.com>
Co-Authored-By: Victor Feyens <vfe@odoo.com>
Co-Authored-By: Thibault Delavallee <tde@odoo.com>

2020-04-21 12:28:52 +00:00

..

__init__.py

[IMP] crm, sales: add crm tags on sale orders

2020-03-23 09:08:47 +00:00

calendar.py

[REF] crm(_iap_lead): use read_group instead of computing len of one2many fields

2020-04-21 12:28:52 +00:00

crm_lead_scoring_frequency.py

[FIX] *: adapt code to comply with new ondelete policy

2019-11-07 08:39:17 +00:00

crm_lead.py

[REF] crm(_iap_lead): use read_group instead of computing len of one2many fields

2020-04-21 12:28:52 +00:00

crm_lost_reason.py

[IMP] crm: better access leads linked to a lost reason

2020-01-27 09:57:03 +00:00

crm_stage.py

…

crm_team.py

[REF] mail: make alias mixin multi-enabled

2020-04-17 06:52:09 +00:00

digest.py

[IMP] crm: improve naming of main crm lead action

2019-09-24 12:14:38 +00:00

res_config_settings.py

[FIX] crm, hr_recruitment: clean manual alias creation

2020-04-17 06:51:39 +00:00

res_partner.py

[REF] crm(_iap_lead): use read_group instead of computing len of one2many fields

2020-04-21 12:28:52 +00:00

res_users.py

[REF] crm : use stored editable r+w fields

2020-03-23 11:42:12 +00:00

utm.py

[IMP] crm: use only one field for leads/opportunities count

2020-01-15 10:02:35 +00:00