Rabbit Creative » Rails

Rails 3 time zones are broken.

Rabbit — Fri, 01 Apr 2011 22:00:21 +0000

ruby-1.9.2-head :001 > RUBY_VERSION
 => "1.9.2" 
ruby-1.9.2-head :002 > Rails.version
 => "3.0.4" 
ruby-1.9.2-head :003 > Time.zone
 => (GMT+00:00) UTC 
ruby-1.9.2-head :004 > Time.zone = '(GMT-08:00) Pacific Time (US & Canada)'
 => "(GMT-08:00) Pacific Time (US & Canada)" 
ruby-1.9.2-head :005 > Time.zone
 => (GMT+00:00) UTC

ruby-1.9.2-head :001 > RUBY_VERSION
 => "1.9.2" 
ruby-1.9.2-head :002 > Rails.version
 => "3.0.4" 
ruby-1.9.2-head :003 > Time.zone
 => (GMT+00:00) UTC 
ruby-1.9.2-head :004 > Time.zone = 'Pacific Time (US & Canada)'
 => "Pacific Time (US & Canada)" 
ruby-1.9.2-head :005 > Time.zone
 => (GMT-08:00) Pacific Time (US & Canada)

Rails 3 destroy migration examples.

Rabbit — Thu, 03 Mar 2011 14:52:17 +0000

rails generate migration name_of_the_migration_you_want_to_destroy
rails destroy migration name_of_the_migration_you_want_to_destroy

No need to fiddle with the timestamp prefix or the “.rb” file extension.

Rails 3 still fucking up field_with_errors.

Rabbit — Tue, 21 Sep 2010 03:47:34 +0000

Wow. I thought the arguments for using SPAN instead of DIV tags were pretty convincing. Alas, those smart guys on the Rails core team think otherwise.

So, fuck them. Here’s one way to fix it in Rails 3:

Inside application.rb:

module Arcade
  class Application < Rails::Application
 
    ActionView::Base.field_error_proc = Proc.new do |html_tag, instance|
      include ActionView::Helpers::RawOutputHelper
      raw %(<span class="field_with_errors">#{html_tag})
    end
 
  end
end

Tap into ActiveRecord’s sanitization methods.

Rabbit — Tue, 20 Apr 2010 17:15:45 +0000

Object instantiation is expensive.

object.association.create(...)

But at the same time you get the power of ActiveRecord’s beautiful sanitization methods. Now you can have that same power without as much overhead.

values = ActiveRecord::Base.send(:sanitize_sql_array, [ '?, ?, ?', x, y, z ])

Familiar syntax is familiar. Now use it.

ActiveRecord::Base.connection.execute(%{INSERT INTO objects (x, y, z) VALUES (#{ values })})

Presto beautiful!

You talk too much.

Rabbit — Tue, 12 Jan 2010 22:18:42 +0000

Trying to dump data from SQLite3 and import that data into MySQL? This post can be summed up thusly:

script/plugin install git://github.com/adamwiggins/yaml_db.git

rake db:dump
rake db:create

Update config/database.yml

rake db:load

But that’s just me. When I look at the commands above I know the context in which they should be used, therefore I want only that which is most pertinent.