Answers.Body: <p>In case anyone has the same version (4.6.7), this was the fix for our issue - Drupal timezone code does not handle UTC correctly - <a href="https://github.com/civicrm/civicrm-core/pull/6576" rel="nofollow">https://github.com/civicrm/civicrm-core/pull/6576</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-15T21:32:07.973Z
Answers.LastActivityDate: 2016-01-15T21:32:07.973Z
Answers.UserDisplayName: Alex Katayama
Answers.Body: <p>It's a timezone issue. Your database and drupal timezone must be same. Sometime it's happen due to Daylight saving time.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-28T02:56:48.780Z
Answers.LastActivityDate: 2015-11-28T02:56:48.780Z
Answers.UserDisplayName: Prem Patel
Body: <p>I hope I have a strange, but straight forward issue -- there's a 1 hour offset SOMETIMES in the created_date field in civicrm_contact table, and what gets outputted in a CiviCRM report (see the attached images).</p>
  
  <p>MySQL is set to use SYSTEM time as well as PHP - ie, and no timezone conflict.</p>
  
  <p>Any suggestions would be greatly appreciated. We are using Drupal 7 + CiviCRM 4.6.</p>
  
  <p><a href="https://i.sstatic.net/JrmP4.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/JrmP4.png" alt="Time in MYSQL"></a></p>
  
  <p><a href="https://i.sstatic.net/98DNL.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/98DNL.png" alt="Time in Detailed Member Report"></a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-26T00:13:50.000Z
Comments.Text: what is your users timezone setting in drupal?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-26T20:07:38.867Z
Comments.Text: It's strange, both were set to Eastern (-4). However, when I switched my timezone to UTC (0) in Drupal, the timestamps were displayed as expected, but now we have that PHP/MySQL timestamp mismatch warning. I also noticed the created_date is set as "TIMESTAMP" in the database, but the format is clearly DATETIME -- is there a reason for this?
Comments.UserDisplayName: Alex Katayama
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-11-26T23:59:22.537Z
Comments.Text: really not sure sorry
Comments.UserDisplayName: petednz - fuzion
Tags: <drupal><civireport><mysql><timezone>
Title: 1 hour discrepancy between created_date field in MySQL and CiviCRM report output
ThreadText: # 1 hour discrepancy between created_date field in MySQL and CiviCRM report output
  
  (Asked by: username_0 on 2015-11-25)
  
  I hope I have a strange, but straight forward issue -- there's a 1 hour offset SOMETIMES in the created\_date field in civicrm\_contact table, and what gets outputted in a CiviCRM report (see the attached images).
  
  MySQL is set to use SYSTEM time as well as PHP - ie, and no timezone conflict.
  
  Any suggestions would be greatly appreciated. We are using Drupal 7 + CiviCRM 4.6.
  
  [![Time in MYSQL](https://i.sstatic.net/JrmP4.png)](https://i.sstatic.net/JrmP4.png)
  
  [![Time in Detailed Member Report](https://i.sstatic.net/98DNL.png)](https://i.sstatic.net/98DNL.png)
  
  **Tags:** drupal, civireport, mysql, timezone
  
  > **Comments:**
  > **username_1**: what is your users timezone setting in drupal?  
  > **username_0**: It's strange, both were set to Eastern (-4). However, when I switched my timezone to UTC (0) in Drupal, the timestamps were displayed as expected, but now we have that PHP/MySQL timestamp mismatch warning. I also noticed the created_date is set as "TIMESTAMP" in the database, but the format is clearly DATETIME -- is there a reason for this?  
  > **username_1**: really not sure sorry  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2016-01-15. Score: 0 | Accepted answer
  
  In case anyone has the same version (4.6.7), this was the fix for our issue - Drupal timezone code does not handle UTC correctly - <https://github.com/civicrm/civicrm-core/pull/6576>
  
  
  ---
  
  ### Answer by username_2 on 2015-11-28. Score: 1
  
  It's a timezone issue. Your database and drupal timezone must be same. Sometime it's happen due to Daylight saving time.
  
  
  ---
  
  