/writing-migrations-dumbo-web-082718

Primary LanguageRubyOtherNOASSERTION

Let's Write Some Migrations

##Objectives

  1. Write your own migrations
  2. Run a migration to create a table
  3. Run a migration to add a column to a table
  4. Run a migration to change something in the table

Creating a table

The first thing we will do is create a table. In db/migrate/01_create_students.rb, write the code to create a table with ActiveRecord. We've created a class for you called CreateStudents.

Next, define a method called change and use the ActiveRecord create_table method within that method to create the table. The table should have a :name column with a type string.

After you finish defining the change method, run the migrations by running rake db:migrate in your terminal.

Adding a column

The next thing we will do is add a couple of columns to the students table we just created. To do this, we will create a second migration file. We cannot add these columns to the existing file. Let's call our new file 02_add_grade_and_birthdate_to_students.rb. It should live in db/migrate just like the first migration.

This new migration will look similar to the previous one. We will need a class that inherits from ActiveRecord::Migration, and we will need to define a change method. Inside #change, instead of create_table, we will use the add_column ActiveRecord method.

Let's add a :grade column and a :birthdate column. The :grade column type should be integer and the :birthdate column type should be string.

Changing a column

Imagine you're creating an incredible web app to send out a birthday greeting on each student's birthday. While building this, you realize you accidentally stored your birthdate data as a string. It would be much easier to work with if the column type was datetime instead. Let's fix that.

Finally, we will change a column type, string to datetime. Same as before, you'll have to create another migration file. This time call it 03_change_datatype_for_birthdate.rb.

Again, same setup as before. Be sure to use the change_column method. It takes three necessary arguments: change_column(table_name, column_name, type).

Active Record 5.x migration syntax update

NOTE: As of Active Record 5.x, we can no longer inherit directly from ActiveRecord::Migration and must instead specify which version of Active Record / Rails the migration was written for. If we were writing a migration for Active Record 5.1, we would inherit from ActiveRecord::Migration[5.1]. Don't worry too much about this until you get to the Rails section. Until then, if you encounter an error like this...

StandardError: Directly inheriting from ActiveRecord::Migration is not supported. Please specify the Rails release the migration was written for:

  class CreateDogs < ActiveRecord::Migration[4.2]

...simply add [4.2] to the end of ActiveRecord::Migration, exactly as the error message instructs.

View Let's Write Some Migrations on Learn.co and start learning to code for free.

View Writing Our Own Migrations on Learn.co and start learning to code for free.

View Writing Our Own Migrations on Learn.co and start learning to code for free.