One thing I have done successfully is to set ENV[TZ] = UTC early
in my config/environment.rb. That ensure the full Rails process is
always in UTC. Time.now will now be the same as Time.now.utc.
Hope that helps!
François Beausoleil
http://blog.teksol.info/
Hello
I did a pull from heroku and into a sqlite3 and it seems like the
datetime fields changed default timezone. suddenly all datetimes are
off by 8 hours.. If I am correct there is 8 hour time difference from
Central US time to GMT+1.
I have set the config.time_zone = 'Copenhagen' in my
Heroku uses PST as its timezone (GMT-8) and rails does not include the
timezone when it creates a timestamp field. Sqlite assumes that all
timestamp values are GMT+0. I believe that's where you get your 8hr
difference.
On Mar 25, 4:46 am, MartOn frode.mel...@gmail.com wrote:
Hello
I did a
I thought rails stores timezones since v2.2?
I am using v2.2.2
But hey.. Maybe I am wrong :-)
/MartOn
On Mar 25, 10:05 pm, Ricardo Chimal, Jr. rica...@heroku.com wrote:
Heroku uses PST as its timezone (GMT-8) and rails does not include the
timezone when it creates a timestamp field. Sqlite
