This project is archived and is in readonly mode.

#632 ✓stale
Bill Bereza

rake db:migrate VERSION=0 does all migrations when already at 0

Reported by Bill Bereza | July 16th, 2008 @ 03:55 PM | in 2.x

Using rails 2.1.0, create a new rails project and make a couple

migrations that create some tables.

Run "rake db:migrate VERSION=0" and you'll see that it runs all the

migrations, even though it should already be at version 0.

This will happen anytime you're at version 0. Doing a normal "rake

db:migrate" followed by two "rake db:migrate VERSION=0" will bring you

back to the latest migration.

You can keep running "rake db:migrate VERSION=0" and it will go back

and forth between the beginning and the end of the migrations.

--

Bill Bereza | Vice President

Atomic Object | http://atomicobject.com

[Ph] +1 616 776 6020 [Fx] +1 616 776 6015

Comments and changes to this ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

People watching this ticket

Pages