c2c-oerpscenario team mailing list archive

[Dukai Gábor <693339@xxxxxxxxxxxxxxxxxx>]

Thank you.

In some cases this prevented using record rules because they were a few
hundred times slower than normal. In some less problematic cases it just
made the gui a bit sluggish even if the values were stored.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/693339

Title:
  Regression: Huge performance decrease with fields.related (v5 and v6)

Status in OpenObject Server:
  Fix Released
Status in OpenObject Server 5.0 series:
  Confirmed

Bug description:
  Hi!

A regression created in jvo@xxxxxxxxxxx-20100202150454-x9kne83yzkjciidw
for v5: http://bazaar.launchpad.net/~openerp/openobject-server/5.0/revision/1950
for v6: http://bazaar.launchpad.net/~openerp/openobject-server/trunk/revision/1844.4.90

If a fields.related with store=True is searched, it doesn't use the stored value but calculates the values like it was not stored at all.
Because of this, for example with a fields.related location_id on stock.picking a search for one location could result in sql queries having 30000 ids instead of a simple stock_picking.location_id in (%s).

There's a stock_location_restrict module in the community addons as an example: http://bazaar.launchpad.net/~openerp-community/openobject-addons/trunk-addons-community/annotate/head%3A/stock_location_restrict/stock.py