Skip to content

checking table existence in Rails’ migrations

by cory on March 27th, 2008

I just refactored a table and in the migration I created for it I first need to drop the table and then create it from scratch, so the first line of self.up is drop_table :table_name. But when I go back and forth over that migration, the second time around the table doesn’t exist (because it got dropped proper in self.down), so I need to check that the table exists before I try to drop it in self.up.

Here’s the function I created to do that check:

 def self.table_exists?(name)
    ActiveRecord::Base.connection.tables.include?(name)
  end

And here’s the new first line of self.up:
drop_table :table_name if self.table_exists?("table_name")

Clean.

From → general, projects, ruby

blog comments powered by Disqus