0

So I jumped onto this Rails project at work and I have my own copy of it running on my local devbox. I tried to run the tests to see what the results were but rake came back complaining that I had 5 outstanding migrations to do first. I first just tried running rake db:migrate but that didn't work due to the migrations trying to create tables that already existed. It was then I realized that these migrations have already been run, but for some reason it thinks it is currently at an older migration.

Is there any way to make Rake move forward in the migration history without doing a rollback and redoing the migration?

grg-n-sox
  • 717
  • 2
  • 5
  • 25
  • Out of interest you could try and execute the following `rake db:drop && rake db:create && rake db:migrate` in your command prompt – Deej Jun 19 '13 at 01:25
  • run `rake db:test:prepare` that should bring the test db up to the same migrations as the development db – house9 Jun 19 '13 at 02:00

2 Answers2

1

You could update schema_migrations table to have the migration numbers that you want to skip. That's the table rails uses to keep track of the migrations that have been run already.

select * from schema_migrations

will give you something like

   version     
----------------
 20121026165533
 20121026183631
 20121212144141
 20130205205009

Add the migration numbers that you want to skip to this table.

usha
  • 28,973
  • 5
  • 72
  • 93
0

You could either:

  1. Delete the migrations in question, make a new set of migrations to take their place (dangerous)

  2. Do the rake db:reset as you mentioned.

I would only suggest 1 if you are the only developer on the project. In reality however, your migrations and seeds should be in such a state as to not warrant this.

I would implore you to take #2, as #1 could result in issues down the track. Your copy of the database should be representative of what you would get if you ran rake db:reset anyway.

Emile Victor
  • 923
  • 1
  • 12
  • 22