diff options
| author | Laurent Mignon (ACSONE) <laurent.mignon@acsone.eu> | 2017-03-08 16:03:54 +0100 |
|---|---|---|
| committer | Martin Trigaux <mat@odoo.com> | 2017-03-09 14:07:58 +0100 |
| commit | 1dea8a53fbe5d064ea6aeae6506df71be00412f5 (patch) | |
| tree | 77d291367e6c06c7e40fc7974d30c7c2bf1694fe /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | e4a0a300cb974bbcbe599770926efe0a385fee0f (diff) | |
[FIX] resource: correct also microsecond information
A lot of methods are designed to work with pure datetime objects as args. If
the value comes from the database it will be rounded at the level of seconds
(0 microsecond). If it comes from a call do datetime.now() / datetime.utcnow()
the datetime object has a value != 0 for its mircroseconds attribute. Therefore
some methods have unpredictable results depending of the origin of the values
manipulated since the microsecond argument is missing into all the calls to
datetime.replace
Closes #15768
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions