Geoff Buesing

Turns out the standard library isn't to blame -- ActiveSupport defines DateTime#to_f, so Time#- coerces the DateTime arg #to_f and assumes we're subtracting sec...

Looking at the historical data, Buenos Aires and Georgetown, Guyana shared the same base UTC offset (-03:00) from 1975 to 1991, which is probably why Windows co...

To answer your question about Mysql DATETIME columns: they're not affected by the Mysql time zone. From the Mysql documentation:

"The current time zone setting ...

@Joachim: thanks for the thorough writeup.

The issue described here with Mysql doing time zone conversions on TIMESTAMP columns. Note that TIMESTAMP columns are...

Applied in master and 2-3-stable. Thanks!

master: http://github.com/rails/rails/commit/2ae8300489aaaaaa65f50f3557090b...
2-3-stable: http://github.com/rails/r...

Aha, ok, I see what the issue is -- the instance of ActiveSupport::TimeWithZone you're creating is storing the time internally as a DateTime (because you starte...

I can't replicate this.

With what arguments are you calling time_ago_in_words to get the error?

Matt Jones is probably right; this looks to be an issue with the database not storing usec.

In your tests, you can try coercing to_a before comparing; usec valu...

TimeZone#utc_offset (called when you call Time.zone.utc_offset) returns just the base UTC offset for the time zone; it doesn't take DST into consideration.

This...

The only valid settings for config.active_record.default_timezone are :utc and :local.

I've seen others make this same error -- they assume default_timezone can...