Yeah, I tried that in my example that I posted but the results aren't then converted back to the users timezone. So if a Product is sitting in the database with created_at = 2009-09-03 02:39:22 UTC (which is 2009-09-02 21:39:22 CDT), it won't come back converted to CDT.
On Sep 3, 11:54 am, Matt Jones <[email protected]> wrote: > This looks like an instance of this bug: > > https://rails.lighthouseapp.com/projects/8994/tickets/2946 > > The quick way to fix it in this case is to convert the incoming > datetime objects to UTC in timeline_created_products. > > --Matt Jones > > On Sep 2, 10:23 pm, JL Smith <[email protected]> wrote: > > > I'm having some trouble getting activerecord to adhere to my timezone > > settings when finding objects based on its created_at field. I > > understand that datetime fields are stored in UTC but it doesn't > > convert the datetimes when it performs the lookup. I basically > > followed Railscasts #106 and I'm using Authlogic for authentication. > > Thanks for any help. > > >http://gist.github.com/180080 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
