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

  • SEARCH
  • Home
  • 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 8807707
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T02:26:02+00:00 2026-06-14T02:26:02+00:00

I created a migration a while ago that I must have forgotten to populate

  • 0

I created a migration a while ago that I must have forgotten to populate or something. I just went to recreate it and got the following:

Another migration is already named add_user_id_to_comments:
foo/db/migrate/20121103004535_add_user_id_to_comments.rb

I’ve run `rake db:migrate’ a bunch of times since and have a handfull of new migrations…

What’s the best way out of this mess?

  • 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-06-14T02:26:03+00:00Added an answer on June 14, 2026 at 2:26 am

    If the old one is completely blank, just delete it. Its absence will not adversely affect anything. If you want to remove all traces, you’ll also want to remove 20121103004535 from your schema_migrations table, but it is not required….

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

Sidebar

Related Questions

I have an ExpenseType object that I have created with the following migration: class
i have this crazy label for each time i create a migration that use
I have created own AMI and registered it on Amazon EC2. But while AMI
I have an iOS app in the AppStore, built with Xcode a while ago,
I have an app that currently has 35 south migrations. These take a while
I have created a new application using Entity Framework 4.3 database migrations. The migrations
I have a problem with relations while using sqlite3 on rails. First i build
I am getting this error when running ./manage.py migrate app_name While loading migration 'whatever.0001_initial':
Hi I created a table for a wiki application that I was doing. It
While migration i migrated the files with a wrong name, and now i rolled

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.