-
- Downloads
[FIX] stock_landed_costs: use list not tuple
ae96f0e introduced an issue because the update of the m2m used a `tuple` instead of a `list` How to reproduce: * Apply only the (Python) code changes done in ae96f0e, keeping the same view (i.e. ignore the changed done to the view in ae96f0e). * Instead of `n=5000` in the compute set `n=1` (it cannot be reproduced with 5000 unless we create enough dummy data). * On a clean v13 db with Landed costs (Accounting + Inventory + Purchase + demo data) * Confirm a Purchase * Create a Landed cost * Try to select a transfer Traceback: ``` ... return f(self, *args, **kwargs) File "/home/odoo/src/odoo/13.0/odoo/sql_db.py", line 250, in execute res = self._obj.execute(query, params) psycopg2.errors.UndefinedFunction: operator does not exist: integer = integer[] LINE 1: ...FROM "stock_picking" WHERE (("stock_picking"."id" in (ARRAY[... ^ HINT: No operator matches the given name and argument types. You might need to add explicit type casts. ``` On the reported issues the traceback occur only for DBs with more than 5000 valid pickings, and for views that use the field `allowed_pickign_ids`. opw-2762355 closes odoo/odoo#84479 X-original-commit: ccd37565 Signed-off-by:Christophe Simonis <chs@odoo.com>
Please register or sign in to comment