odoo/addons/analytic
Olivier Dony 2d83656c0f [FIX] analytic: multi-path name_search should properly handle `limit`
Due to commit 1576bc9891,
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.
2015-07-27 12:58:48 +02:00
..
i18n [I18N] Update translation terms from Transifex 2015-07-19 02:01:00 +02:00
security [REM] bunch of nonsensical @model + @ref 2013-04-29 14:43:33 +02:00
__init__.py
__openerp__.py [IMP] Updated website urls on modules and info page 2014-08-26 21:40:18 +02:00
analytic.py [FIX] analytic: multi-path name_search should properly handle `limit` 2015-07-27 12:58:48 +02:00
analytic_data.xml [IMP] mail.message.subtype: set some subtypes as not followed by default, to avoid leaking information. 2013-01-30 14:58:25 +01:00
analytic_sequence.xml [IMP]remove tabs and add spaces instead of them 2012-06-28 12:10:05 +05:30
analytic_view.xml [MERGE] forward port of branch saas-3 up to 4a3c471 2015-03-09 12:03:22 +01:00