Regression: Huge performance decrease with fields.related with store=True/{}(v5 and v6)

We Let the Framework team decide.

Thanks.

Dukai,
Thanks for the detailed analysis and tracking of the commits in 5.0 and trunk!
This has been corrected in trunk by revision 3148 <email address hidden>.

I am assigning the port of this fix in 5.0 to the maintenance team, and this will give Jay the opportunity to review his original commit and explain why he disabled the use of the database column for search on function fields that have fnct_search.
Related fields are an example of a function field that always has a "fnct_search" method, but it should not be used if the field is stored, because searching the stored column in the database will be faster 99% of cases (and we can't detect the cases where it could possibly be slower anyway)

Thanks!

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.

Thanks Dukai and Olivier.

I corrected my previous commit by revision 2164 <email address hidden>.

I might have not considered any test case for related field with store attribute,as this is not really a common practice to use.

Thanks again.