diff options
| author | XavierDo <xdo@odoo.com> | 2018-06-29 14:05:12 +0200 |
|---|---|---|
| committer | XavierDo <xdo@odoo.com> | 2018-07-11 10:11:14 +0200 |
| commit | f74f5edc7778a3afacc454c31993ac8502d3d0ee (patch) | |
| tree | c5a0a0cfb4beb8a80e27b17690aec1f22963a976 /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | 94c027efdd9cf180f4ebcf7faadae2af6645d191 (diff) | |
[FIX] calendar: correct domain computation for recurring events
The custom computation for domain applied on recurring event
was assuming that a leaf value was true. This can lead to miscomputation.
Context:
For a domain like
'|',
('start', '>=', '2018-06-28 23:59:59'),
('allday', '=', True),
the domain will be transformed into
'|',
'|',
('start', '>=', '2018-06-28 23:59:59'),
'&',
('recurrency', '=', 1),
('final_date', '>=', '2018-06-28 23:59:59'),
('allday', '=', True],
In order to fetch recurring event with date that COULD match the domain.
Then, the custom evaluation will filter the generated virtual ids with
the base domaine, replacing leaf not specific to bounds by true,
leading to a domain like:
'|',
('start', '>=', '2018-06-28 23:59:59'),
True,
Also well known as "True"
Therefore, all recurring event virtual ids will be kept.
Solution:
This fix proposes to fetch the leaf values from the database to ensure
the consistency of the domain.
Thanks to RLI for the help.
Task: #1858076
PR: #25544
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
