Yeah. It (just) works for me™ too. What about in a brand new app? On Oct 26, 2010 6:28 PM, "Guyren Howe" <guy...@gmail.com> wrote: > On Oct 26, 2010, at 6:03 PM, Jason King wrote: >> And you have this in your Application class? >> >> config.time_zone = 'Pacific Time (US & Canada)' >> >> If so, some gem you're not taking into account that might be messing with the before/after chain? > > I don't think so. It clearly *has* that set when I get to the part of the code that is doing comparisons with created_at. What appears to be happening is that it's getting it wrong at create time. I'm not messing with that at all; I'm just relying on the magic behavior when the field is called created_at. > > It's just weird. I could dive into the code at save time, but that's a tedium I was hoping to avoid. > > Not urgent; I'm manually working around the conversion. But it's annoying, and something I'd like to understand. > > Haven't found a good reference on Time Zones in Rails 3. Most of the stuff just says "Hey, set your time zone, and everything works like magic", which is just annoying right now. :-) > > -- > SD Ruby mailing list > sdruby@googlegroups.com > http://groups.google.com/group/sdruby
-- SD Ruby mailing list sdruby@googlegroups.com http://groups.google.com/group/sdruby
