Contributors mailing list archives
contributors@odoo-community.org
Browse archives
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
by
Tecnativa. S. L., Pedro M. Baeza
If talking about picking generation, I wouldn't do reserve at that time, and do a general "reserve round" at the end of the batch, and thus, you remove the quant lock constraint.
Regards.
Reference
-
ERROR: could not serialize access due to concurrent update (case using Job Queue)
byEcosoft Co. Ltd., Kitti Upariphutthiphong- 04/03/2024 14:11:51 - 0-
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byEcosoft Co. Ltd., Kitti Upariphutthiphong- 04/03/2024 16:59:56 - 0 -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byTecnativa. S. L., Pedro M. Baeza- 04/03/2024 15:28:39 - 0 -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byTherp, Tom Blauwendraat- 04/03/2024 15:22:08 - 0 -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byAkretion France, Florian da Costa- 04/03/2024 15:13:55 - 0 -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
byEcosoft Co. Ltd., Kitti Upariphutthiphong- 04/03/2024 15:00:42 - 0 -
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)
by "Adam Heinz" <adam.heinz@metricwise.com> - 04/03/2024 14:31:20 - 0
-
