diff options
| author | Olivier Dony <odo@openerp.com> | 2013-07-01 18:35:32 +0200 |
|---|---|---|
| committer | Olivier Dony <odo@openerp.com> | 2013-07-01 18:35:32 +0200 |
| commit | 9b6f5dca9a63230ae45e16a25c4acc54dd54b65b (patch) | |
| tree | 47db220250a417254623a23250b186bc00674844 /addons/procurement/procurement_data.xml | |
| parent | 00c1c134fc6d4bcf7be608cc18fbdf0669dbc783 (diff) | |
[FIX] procurement: background procurement scheduler should be working in batch mode, with one transaction per order
A programming error during an older refactoring lead to
the scheduler working with a single monolithic transaction.
This could cause unnecessary resource contention, plus
undesired rollback of all previous operations in the event
of an exception during scheduling.
bzr revid: odo@openerp.com-20130701163532-8bekn7sbb99ua08c
Diffstat (limited to 'addons/procurement/procurement_data.xml')
| -rw-r--r-- | addons/procurement/procurement_data.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/addons/procurement/procurement_data.xml b/addons/procurement/procurement_data.xml index 6a83d525c68..52503e76c44 100644 --- a/addons/procurement/procurement_data.xml +++ b/addons/procurement/procurement_data.xml @@ -12,7 +12,7 @@ <field eval="False" name="doall"/> <field eval="'procurement.order'" name="model"/> <field eval="'run_scheduler'" name="function"/> - <field eval="'(False,)'" name="args"/> + <field eval="'(False,True)'" name="args"/> </record> <record id="sequence_mrp_op_type" model="ir.sequence.type"> |