View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
0001657 | Pending Requests | [All Projects] Tasks | public | 2015-08-04 04:01 | 2017-11-25 00:29 | ||||||||
Reporter | opto | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||||
Status | new | Resolution | open | ||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001657: dbfnNowWithTZ?? | ||||||||||||
Description | in many plces, I find $q->addUpdate('task_updated', "'" . $q->dbfnNowWithTZ() . "'", false, true); why dbfnNowWithTZ? As compared to Server time, it is not the time in Server TZ. or rather, looking at the code: isn't the function Name a misnomer? Shouldn't it be called dbfnNowInUTC? As compared to user TZ or Server TZ, etc., it does not give time in their TZ | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files |
|
![]() |
|||
Date Modified | Username | Field | Change |
---|---|---|---|
2015-08-04 04:01 | opto | New Issue | |
2016-04-30 23:00 | opto | Project | v3.3 Release => v3.4 Release (Current) |
2016-04-30 23:00 | opto | Category | Core Infrastructure => General |
2016-12-27 23:38 | caseydk | Category | General => Tasks |
2017-11-25 00:29 | caseydk | Project | v3.4 Release (Current) => Pending Requests |