DEV Community: Hardik Radadiya

Rails Database Migrations: Tips, Tricks, and Best Practices

Hardik Radadiya — Tue, 03 Oct 2023 09:09:49 +0000

If you’re a Ruby on Rails developer, you’re probably no stranger to the concept of migrations. Migrations are an essential part of managing your application’s database schema, allowing you to make changes to your database structure in an organized and version-controlled manner. In this guide, we’ll dive deep into migrations in Rails, exploring various scenarios and commands that will help you wield the power of migrations effectively.

Adding Columns to Existing Tables
Scenario 1: Adding a Column with an Index
Let’s say you want to add an ‘email’ column to your ‘users’ table and index it for faster search operations. Here’s how you can do it:

rails generate migration AddEmailToUsers email:string:index

This command generates a migration file, and you can add the following code to it:

def change
  add_column :users, :email, :string
  add_index :users, :email
end

This migration adds the ‘email’ column to the ‘users’ table and creates an index on it for improved query performance.

Scenario 2: Adding Multiple Columns
Adding multiple columns to a table is also straightforward. Suppose you want to add ‘name,’ ‘salary,’ and ‘email’ columns to the ‘users’ table:

rails generate migration AddDetailsToUsers name:string salary:decimal email:string

The generated migration file will include code to add all three columns to the ‘users’ table.

Modifying Columns
Scenario 3: Renaming a Column
To rename a column in a table, you can use a migration. Let’s say you want to rename a column named ‘old_column’ to ‘new_column’.

rails generate migration RenameColumnName
In the generated migration file, you can use the rename_column method:

def change
  rename_column :table_name, :old_column, :new_column
end

This code will change the name of the column from ‘old_column’ to ‘new_column’.

Removing Columns
Scenario 4: Removing a Column
If you need to remove a column from a table, Rails migrations can help with that too. Let’s say you want to remove the ‘name’ column from the ‘users’ table:

rails generate migration RemoveNameFromUsers name:string

The generated migration file will include the code to remove the ‘name’ column.

Managing Relationships
Scenario 5: Adding a Foreign Key
In Rails, managing relationships between tables is crucial. Suppose you have a ‘User’ model that has many ‘Upload’ records, and you want to add a foreign key to the ‘uploads’ table:

rails generate migration AddUserToUploads user:references

You can also explicitly specify the foreign_key: true option:

def change
  add_reference :uploads, :user, foreign_key: true
end

This migration adds a ‘user_id’ column to the ‘uploads’ table, creating a foreign key relationship with the ‘users’ table.

Scenario 6: Adding a Unique Constraint
To enforce uniqueness on a column, you can create a migration like this:

rails generate migration AddEmailToUsers email:string:uniq

The generated migration file will add a ‘unique’ index on the ‘email’ column in the ‘users’ table, ensuring that no two users can have the same email address.

Creating Join Tables
Scenario 7: Creating a Join Table
Join tables are used to represent many-to-many relationships between models. Suppose you have ‘Customer’ and ‘Product’ models, and you want to create a join table to track which products each customer has purchased:

rails generate migration CreateJoinTableCustomerProduct customer product

The generated migration file will create a join table called ‘customer_product’ and set up the necessary indexes.

Conclusion
Database migrations are a powerful tool in Ruby on Rails, allowing you to manage your database schema efficiently. Whether you need to add columns, modify data types, remove columns, manage relationships, or create join tables, Rails migrations provide a structured way to make these changes while keeping your application’s data integrity intact.

By mastering migrations, you’ll be better equipped to handle database changes in your Rails projects, ensuring a smooth and organized development process. So, don’t hesitate to use these migration commands to shape your database schema and make your application even more powerful.

What is slug in rails ?

Hardik Radadiya — Thu, 09 Jan 2020 12:46:48 +0000

Rails js load issues use turbolinks gem.

Hardik Radadiya — Fri, 13 Dec 2019 10:14:37 +0000

Active admin print current user.email but single row

Hardik Radadiya — Wed, 23 Oct 2019 08:36:56 +0000

form title: 'Edit Leave Application' do |f|
inputs 'LeaveApplication' do

  f.li do
    f.label :user_id
    f.span f.object.user.email
  end

  f.input :title
  f.input :description
  f.input :status
  f.input :leave_credit
  f.input :leave_type
  f.input :half_leave_session
end
actions

end
end

DropboxAuthError: Error getting request token. Is your app key and secret correctly set? Server returned 400: Bad Request

Hardik Radadiya — Thu, 10 Oct 2019 07:21:24 +0000

rake aborted! DropboxAuthError: Error getting request token. Is your app key and secret correctly set? Server returned 400: Bad Request.

/home/test/.rvm/gems/ruby-2.3.1/gems/dropbox-sdk-1.6.5/lib/dropbox_sdk.rb:277:in get_token'

/home/test/.rvm/gems/ruby-2.3.1/gems/dropbox-sdk-1.6.5/lib/dropbox_sdk.rb:293:inget_request_token'

/home/tesr/.rvm/gems/ruby-2.3.1/gems/dropbox-sdk-1.6.5/lib/dropbox_sdk.rb:299:in get_authorize_url'

/home/test/.rvm/gems/ruby-2.3.1/gems/paperclip-dropbox-1.3.2/lib/paperclip/dropbox/rake.rb:11:inauthorize'

/home/test/.rvm/gems/ruby-2.3.1/gems/paperclip-dropbox-1.3.2/lib/paperclip/dropbox/tasks.rake:11:in block (2 levels) in '

/home/test/.rvm/gems/ruby-2.3.1/gems/rake-12.3.3/exe/rake:27:in'

/home/test/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in eval'

/home/test/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in'

Tasks: TOP => dropbox:authorize

rake dropbox:authorize APP_KEY=81zjdh4nfctpdq7 APP_SECRET=mxjs2y3bkeppmsy ACCESS_TYPE = app_folder.

Hardik Radadiya — Wed, 02 Oct 2019 11:16:25 +0000

rake aborted!
DropboxAuthError: Error getting request token. Is your app key and secret correctly set? Server returned 400: Bad Request.
/home/richard/.rvm/gems/ruby-2.3.1/gems/dropbox-sdk-1.6.5/lib/dropbox_sdk.rb:277:in get_token' /home/richard/.rvm/gems/ruby-2.3.1/gems/dropbox-sdk-1.6.5/lib/dropbox_sdk.rb:293:inget_request_token'
/home/richard/.rvm/gems/ruby-2.3.1/gems/dropbox-sdk-1.6.5/lib/dropbox_sdk.rb:299:in get_authorize_url' /home/richard/.rvm/gems/ruby-2.3.1/gems/paperclip-dropbox-1.3.2/lib/paperclip/dropbox/rake.rb:11:inauthorize'
/home/richard/.rvm/gems/ruby-2.3.1/gems/paperclip-dropbox-1.3.2/lib/paperclip/dropbox/tasks.rake:11:in block (2 levels) in <main>' /home/richard/.rvm/gems/ruby-2.3.1/gems/rake-12.3.3/exe/rake:27:in'
/home/richard/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in eval' /home/richard/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in'
Tasks: TOP => dropbox:authorize