That sounds reasonable -- ActiveRecord could set the connection timezone to UTC when AR::Base.default_timezone is :utc, and not set it to anything (i.e., assume the system local timezone is correct) when :local.
Solutions have been offered before for accomodating timestamp with timezone, but they have involved adding another timezone configuration and/or Rails TimeZone -> DB time zone mapping logic to the framework. This is much cleaner. Assuming this doesn't take much code, and doesn't negatively impact performance, I'm +1 on the idea. On Mon, Jan 18, 2010 at 6:18 PM, Jack Christensen <[email protected]>wrote: > The current Rails practice with PostgreSQL is to use timestamp without > zone and use ActiveRecord's time zone handling. This works fine for > Rails but makes it slightly inconvenient for ad hoc, local time queries > outside of Rails. I believe there is a way to get the best of both > worlds. If when creating the connection, ActiveRecord set the connection > time zone to UTC then Rails could handle time zones its way and other > clients could use PostgreSQL's time zone handling. > > Is there any interest in a patch to this effect? > > > Jack > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-core%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
