From 85982317630975aa3e4a87eb130a764b2ae78e2d Mon Sep 17 00:00:00 2001 From: Martin Trigaux Date: Thu, 22 Jan 2015 14:32:55 +0100 Subject: [PATCH] [FIX] purchase: maximum recursion when write on minimum_planned_date Do not write on the function field when you are writing on the function field. - Now you do know what orders is right? - I think I know... - Orders is orders. - I guess no one ever taught you not to use the word you're defining in the definition. ~~Lucky Number Slevin --- addons/purchase/purchase.py | 1 - addons/purchase/test/process/edi_purchase_order.yml | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/addons/purchase/purchase.py b/addons/purchase/purchase.py index ffdda3b1829..3519ef3e6a2 100644 --- a/addons/purchase/purchase.py +++ b/addons/purchase/purchase.py @@ -65,7 +65,6 @@ class purchase_order(osv.osv): ('order_id', '=', po.id), '|', ('date_planned', '=', po.minimum_planned_date), ('date_planned', '<', value) ], context=context) pol_obj.write(cr, uid, pol_ids, {'date_planned': value}, context=context) - self.pool.get('purchase.order').write(cr, uid, po.id, {'minimum_planned_date': value}, context=context) self.invalidate_cache(cr, uid, context=context) return True diff --git a/addons/purchase/test/process/edi_purchase_order.yml b/addons/purchase/test/process/edi_purchase_order.yml index 6d585d69c65..bb34c49bc06 100644 --- a/addons/purchase/test/process/edi_purchase_order.yml +++ b/addons/purchase/test/process/edi_purchase_order.yml @@ -5,6 +5,7 @@ partner_id: base.res_partner_3 location_id: stock.stock_location_3 pricelist_id: 1 + minimum_planned_date: '2011-08-31' order_line: - product_id: product.product_product_33 product_qty: 10.0