diff options
| author | Denis Ledoux <dle@odoo.com> | 2016-04-21 11:01:05 +0200 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2016-04-21 11:06:46 +0200 |
| commit | 9dd373d1323d35c13b3c259f5aa037623ba9ae33 (patch) | |
| tree | eb799c6f56301fd437f76896fac18f82fa3485c0 /addons/web/static/src/js/framework/data.js | |
| parent | a3a8bfb06003d25de62eefd4a2dd5a9e887fcdaa (diff) | |
[FIX] calendar: Partial revert of b7e393a71a964afab7c30d11f5312d617947f275
The above revision allow to edit an event with a start date
greater than the stop date.
This issue was solved by the revision
6c78541978336ae8ad4dc43f7051c19bf1ad4f7d
that the above revision reverts.
The reason why the constraint on
`event.start` and `event.stop` was replaced
by a constraint on
`event.start_datetime` and `event.stop_datetime`
and
`event.start_date` and `event.stop_date` are explained
in 6c78541978336ae8ad4dc43f7051c19bf1ad4f7d:
Basically, `start` and `stop` are computed fields,
that are not recomputed in time, before the constraint is checked.
Besides, the revision b7e393a71a964afab7c30d11f5312d617947f275
re-set the constraint on `start` and `stop`, but forget
to replace the fields in the constraint definition:
```
(_check_closing_date, 'Error ! End date cannot be set before start date.',
['start_datetime', 'stop_datetime', 'start_date', 'stop_date'])
```
opw-673297
Diffstat (limited to 'addons/web/static/src/js/framework/data.js')
0 files changed, 0 insertions, 0 deletions
