Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6639391
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T23:32:55+00:00 2026-05-25T23:32:55+00:00

I have a Rails app running over a MySql DB. Is there a way

  • 0

I have a Rails app running over a MySql DB.

Is there a way to consolidate migrations?
for example:

lets say I have a very large table called members and I create a migration to add column name to that table, later on I create another migration that adds another field address and adds index to the address field.

when i run the migration now, it will change the table 3 times: add name, add address and add index. and in each of the times, the alter table command will actually create a new table, copy all the data to it and drop the old table.

in my case, the members table is very big, over 10M records so each alter takes a few hours.

is there a way to consolidate the changes into one alter?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T23:32:56+00:00Added an answer on May 25, 2026 at 11:32 pm

    Your question is a bit difficult to understand, as you’re not limited to one operation per migration.

    you can easily do :

    class AddNameAddressAndIndexToMembers < ActiveRecord::Migration
      def up
        change_table :members do |t|
          t.string :name
          t.text :address
          t.index :name
        end
      end
    
      def down
        change_table :members do |t|
          t.remove_index :name
          t.remove :name, :address
        end
      end
    end
    

    just reverse your migrations, delete previous migration files, run this migration and all should be well.

    Now, if you mean that these are old migrations, it can be tricky because you don’t want to reverse tons of migrations. But what do you want to achieve ? if you only need to deploy, use the current schema.rb with rake db:schema:dump and rake db:schema:load

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a rails app running on port 3000. The page in question has
I have a rails app running on passenger standalone, which is working perfectly. I
I have a Rails app (running 3.2.2) and I want to cache my users'
I have a ruby on rails app running a server and sometimes it needs
I have a Ruby on Rails app running on my server, and I can't
I have a single-threaded Rails app running on thin in single-threaded mode on Heroku
I have an app running Rails 2.3.5 that has a JSON API for much
We have a web app running on Rails, using Devise and OmniAuth for user
I have a rails app running on Heroku. I am using paperclip for some
I have a rails app which is already running with some users, users that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.