# Problem with migration number

**URL:** <https://www.ruby-forum.com/t/problem-with-migration-number/157255>\
**Category:** Rails\
**Created:** [January 8, 2009, 10:13pm UTC](https://www.ruby-forum.com/t/problem-with-migration-number/157255 "2009-01-08T22:13:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wickie](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/ba9def/32.png) [@wickie](https://www.ruby-forum.com/u/wickie)\
**Post date:** [January 8, 2009, 10:13pm UTC](https://www.ruby-forum.com/t/problem-with-migration-number/157255/1 "2009-01-08T22:13:36Z")

</div>

I have recently had to reload my computer. I don’t know if this if  
relevant at all to this problem, but wanted to mention it.

I have an application that I’m needing to make some changes to. To  
prepare for it, I’m doing a new migration. In the db/migrate directory,  
the last migration was 019\_… My new migration is 020\_…

The problem that I’m having is that rake seems to want to rerun  
migrations beginning with 001. This causes it to error off. I’ve looked  
at schema\_info and schema\_migrations in the database. Both have their  
version set to 19.

What would be causing this? It would be a snap to go into mysql and just  
do the migration manually, but I’d rather stay in the rails framework.

Thanks in advance  
—Michael