title: Why doesn't `config.time_zone` seem to do anything?
body: <p>In <code>application.rb</code>, it says:</p>
  
  <blockquote>
    <p>Set Time.zone default to the specified zone and make Active Record
    auto-convert to this zone.
    Run "rake -D time" for a list of tasks for finding time zone names.
    Default is UTC.</p>
  </blockquote>
  
  <p>But setting <code>config.time_zone = 'Central Time (US &amp; Canada)'</code> or <code>config.time_zone = 'Eastern Time (US &amp; Canada)'</code> has no effect - the <code>created_at</code> field in a model is stil being saved in UTC.</p>
  
  <p>According to <a href="http://railsforum.com/viewtopic.php?pid=81822#p81822" rel="noreferrer">this railsforum answer</a>:</p>
  
  <blockquote>
    <p>config.time_zone just lets rails know
    that your server is set to this
    timezone so when it writes dates to
    the database it can properly convert
    it to UTC.</p>
  </blockquote>
  
  <p>If that is true, then why is it that when my system time is <code>Pacific Time (US &amp; Canada)</code> and <code>config.time_zone = 'Central Time (US &amp; Canada)'</code> or <code>config.time_zone = 'Eastern Time (US &amp; Canada)'</code>, that the <code>created_at</code> time is the correct UTC? Should it not be incorrect?!</p>
  
  <p>Because, if the PST time is 8 PM, then EST is 11 PM and UTC is 4 AM.
  Presuming that Rails does <code>Time.now</code>, that would be 8 PM. And we told Rails that the server is in EST. So, 8 PM would be EST time as far as Rails is concerned and the UTC would then be 5 AM UTC, which would be incorrect (because the actual time is 8 PM PST/11 PM EST, which is 4 AM UTC)</p>
  
  <p>What's going on here?</p>