summaryrefslogtreecommitdiff
path: root/addons/analytic_user_function/analytic_user_function.py
diff options
context:
space:
mode:
authorOlivier Dony <odo@openerp.com>2013-09-06 15:49:50 +0200
committerOlivier Dony <odo@openerp.com>2013-09-06 15:49:50 +0200
commitfe15a49f0e6ba44daf3c173f6df77733a7398be2 (patch)
treede1cab5c0c31f48cba7a9f0655e9f0e5185e3c79 /addons/analytic_user_function/analytic_user_function.py
parent7de48c9694db59c86a823bac3e7a04b9f270872b (diff)
parent95b7d5bcaf82bf3332c5e118a4ed8ba5a297b215 (diff)
[MERGE] res.partner: current name_search() implementation tends to skip a few valid results during early autocompletion - mitigation attempt
The main reason for the semi-random behavior observed during auto-completion is the missing ORDER BY clause in the pre-filtering SQL query. The ORDER BY clause is expensive but inevitable if we want to apply a correct LIMIT, otherwise we would return random `limit` results among all the possible matches. The current SQL query seems convoluted due to the duplicated CASE clause but it performs slightly better than the equivalent CTE-based (WITH...) query, so it was preferred. There is still a chance of returning too few results due to double limit application, as further discussed in bug 1203727 lp bug: https://launchpad.net/bugs/1203727 fixed bzr revid: odo@openerp.com-20130906134950-gi0szic3uw3onyuv
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function.py')
0 files changed, 0 insertions, 0 deletions