Hello and thanks for any insight into this!
I am working on an installation of Sugar and have uncovered a very bizarre issue. Datetimes are being stored in the MySQL database 35 minutes after GMT.
The server is set to UTC and synced with NTP.
All three of these output the correct UTC time, but when I edit a record and then check the date_modified moments later (via the api) it is off by exactly 35 minutes.
1. $ date -u
2. mysql> select UTC_TIMESTAMP();
3. make a file named time.php, put this code into it and then execute it: $ php time.php
PHP Code:<?php
date_default_timezone_set('UTC');
echo date('G:i:s');
?>
It seems that API retrieves the exact date in the database without doing any timezone transformations. Is that true?
The weirdest part is that the result is off by 35 minutes. If it was a factor of an hour, or even 15 minute interval I could assume it was a timezone issue, but this seems like Sugar is adding 35 minutes to GMT.
What method does Sugar use to get the GMT time? Does it use a php method? Any ideas where to look next for tracking this down?
Thank you so much for any help with this.


LinkBack URL
About LinkBacks



Reply With Quote

Bookmarks