When dropping a database table in a migration all data contained within the dropped table will be lost as well. This is to be expected since the table schema no longer exists. However, it is possible to make such a migration reversible so that at least the database structure is preserved.

The expectation here is that we can run rails db:migrate followed by rails db:rollback and recover the previous table’s structure.

I'm using Rails 5 in the above example which makes rake commands consistent with rails commands. This means that any rake command such as rake db:migrate has a counterpart of rails db:migrate.

A naive first approach might look something like the following:

class DropTableWidgets < ActiveRecord::Migration[5.0]
  drop_table :widgets

Unfortunately, the above results in the following errors after attempting to rollback the drop migration.

DropTableWidgets: reverting ==========
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:

To avoid mistakes, drop_table is only reversible if given options or a block (can be empty).

Caused by:

As in the error message says above, drop_table can be reversible if you specify options.

Let’s specify the specific columns that were on the original table as part of the drop table block.

class DropTableWidgets < ActiveRecord::Migration[5.0]
  drop_table :widgets do |t|
    t.string name
    t.text description

    t.timestamps null: false
    t.index :name, unique: true

With the addition of the table columns we can now rollback the database structure and retain the its original schema. Now we can migrate and rollback at will without worrying about losing the widgets table.

« Previous Post
Deploying a jekyll blog to github pages with custom plugins and TravisCI
Next Post »
Enable ESLint for SublimeLinter while using asdf for version management

Join the conversation

comments powered by Disqus