diff options
| author | Olivier Dony <odo@openerp.com> | 2015-07-24 16:37:19 +0200 |
|---|---|---|
| committer | Olivier Dony <odo@openerp.com> | 2015-07-27 12:58:48 +0200 |
| commit | 2d83656c0fe8d6c37913a19a73aa5a6e65acc72a (patch) | |
| tree | ebe865d253e91f956b68add29d00f749c7fd52e3 /addons/analytic_user_function/analytic_user_function_view.xml | |
| parent | b2193e6734ab00c9434a159c12119bc49f3f50aa (diff) | |
[FIX] analytic: multi-path name_search should properly handle `limit`
Due to commit 1576bc98919c1ae93e66f902fb5c700c61c2b6cf,
when name_search() is called on analytic accounts with
multiple path components (e.g. A/B/C), the intermediary
searches are done without the extra domain criterions,
because they should only apply to the leaf.
However because the limit was applied for each step
of the multi-path search, it was quite likely that
no valid results were found in the final filtering,
returning no result at all.
In fact the intermediary steps should not apply the
limit at all, because the leaves we're looking for
may actually be located under parents that are not
found when the limit is applied on each step.
This commits removes the limit (hopefully without
too much of an extra penalty for large databases)
It also introduces a better fallback in case the
multi-path search did not produce any result,
for example if the name of the lead really contains
a '/', and it was not meant to be a path separator.
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function_view.xml')
0 files changed, 0 insertions, 0 deletions
