From 9b6f5dca9a63230ae45e16a25c4acc54dd54b65b Mon Sep 17 00:00:00 2001
From: Olivier Dony <odo@openerp.com>
Date: Mon, 1 Jul 2013 18:35:32 +0200
Subject: [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
---
 addons/procurement/procurement_data.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'addons/procurement/procurement_data.xml')

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">
-- 
cgit v1.2.3