[6.1/7.0/trunk][purchase] changing PO partner_id after order is saved keeps corrupted partner_id at order_line level (fields.related)

[Raphaël Valyi - http://www.akretion.com]

How to reproduce:

on new install with demo data on head v7:

Create a new purchase order with one purchase order line.
Save the purchase order.
Take the purchase order id X from the URL and look at the result of this SQL query:
select partner_id from purchase_order_line where order_id=X;

This gives you Y the partner_id of the purchase order which is expected.

Now edit the purchase order again, change the partner and save it. Run the same SQL query again.
KABOOM! this gives you the old partner_id id which is now corrupted!

I think the problem comes from the fact this is a fields.related with store=True and no proper cache invalidation function. This is a crazy bug because all SQL or ORM using that related field will give corrupted results once you change a purchase order partner, which is something pretty common.

[Yann Papouin (yann-papouin)]

SQL Query to fix existing data:

UPDATE purchase_order_line
   SET partner_id = purchase_order.partner_id
  FROM purchase_order
 WHERE purchase_order_line.order_id = purchase_order.id
   AND purchase_order_line.partner_id <> purchase_order.partner_id;

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

Hello, as a note, a similar issue has been reported for sale order lines on Github: https://github.com/odoo/odoo/issues/1629