diff options
| author | Rémy Voet (ryv) <ryv@odoo.com> | 2020-12-11 14:00:03 +0000 |
|---|---|---|
| committer | Rémy Voet (ryv) <ryv@odoo.com> | 2020-12-11 14:25:45 +0000 |
| commit | f8861e6a63fcd85295affdea4b525af753234b14 (patch) | |
| tree | 3c7920b04e8cff08573fd6920c43134ae1b3b208 /doc/reference/javascript_reference.rst | |
| parent | f01eb942716800921148b5de8d6bc4140d122912 (diff) | |
[FIX] stock: fix performance of forecasted when lot of locations
In the DB with a warehouse with a lot of stock location.
The forecasted widget return a traceback due to a memory error due
to the `_get_domain_locations_new`
(`_get_report_lines`->`read(['qty_available'])`->`_compute_quantities`
->`_compute_quantities_dict`->`_get_domain_locations`)
how returns a extremely long domain (one expression
by location in the context) to compute child location.
But the locations (put in the context) contain already
children locations because of
`('id', 'child_of', warehouse.view_location_id.id)`.
TO SOLVE
Instead of adding location in the context
(for fix 1aa6a323e04232d24175593718637c6dac295eb9),
add the warehouse in the context before
calling the `_get_report_lines` in the `_compute_forecast_information`.
closes #61666
closes odoo/odoo#63217
Signed-off-by: William Henrotin <Whenrow@users.noreply.github.com>
Diffstat (limited to 'doc/reference/javascript_reference.rst')
0 files changed, 0 insertions, 0 deletions
