Project

General

Profile

Actions

Defect #10996

closed

Time zones lost when upgrading from Redmine 1.4 to 2.0

Added by Jack Christensen almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Database
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

It seems that previous versions of Redmine stored times in database in local time. In 2.0 it stores it in UTC. This causes all old times to be offset by the time zone. e.g. A task I entered right before the upgrade showed as being 5 hours old.

I just ran SQL to update the time stamps appropriately, but it might be nice to have this done automatically.

Here's the script I used (PostgreSQL):

select 'UPDATE ' || table_name || ' SET ' || column_name || ' = ' || column_name || '::timestamptz at time zone ''utc'' WHERE ' || column_name || ' < ''2012-05-22 10:40:00'';'
from information_schema.columns
where table_schema='public'
  and data_type like 'timestamp without time zone'

The hard-coded time is the time that the upgrade occurred so as not to update times from after the upgrade.


Related issues

Related to Redmine - Defect #14658: Wrong activity timezone on user pageClosedJean-Philippe Lang

Actions
Actions #1

Updated by Etienne Massip almost 12 years ago

  • Category set to Database
Actions #2

Updated by Xinruo Sun almost 12 years ago

I confirm the issue when upgrading from 1.1 to 2.0, with sqlite3 as the database. All redmine time information is incorrect.

Actions #3

Updated by Jean-Philippe Lang almost 12 years ago

  • Status changed from New to Resolved
  • Target version set to 2.0.1
  • Resolution set to Fixed

Rails 3 uses UTC timestamps by default. I've restored the previous behaviour for compatibility with Redmine 1.x in r9719 (timestamps stored in local timezone).
If you want to use UTC timestamps instead, just change config.active_record.default_timezone to :utc.

Actions #4

Updated by Jean-Philippe Lang almost 12 years ago

  • Status changed from Resolved to Closed
Actions #5

Updated by Go MAEDA about 7 years ago

  • Related to Defect #14658: Wrong activity timezone on user page added
Actions

Also available in: Atom PDF