If this is on your development machine only, there are a few options:
1) Drop the database and recreate it, using the present migrations. Take the following steps
rake db:drop
rake db:create
rake db:migrate
This will recreate the database using only the present migrations, like a clean start, and since the 000
migration file is gone, it will not be recreated.
2) rollback all the migrations, from your list only two, and then run the migrations again
rake db:rollback STEP=2
rake db:migrate
this does nearly the same as the previous option, I guess it depends on how migrations you need to rollback to see which is the easiest.
These will only work if the migration with version '000' is NOT already deployed, or migrated by your fellow developers (when working in a team). If that is the case, I would consider the following options:
- squash all migrations into one (e.g. load the schema file from a migration)
- create a new migration-file with the missing-number and ... restore what it contained before (even if it was empty?)