2.0.2 migrations seem totally broken

I have a Rails app running under 2.0.2. I created the app with 2.1, but
eventually ran into some bugs and set the app to run at 2.0.2, and
commented out the 2.1 initializers.

I've created and dropped the database a few times so I could have a
clean slate.

The issue is the version number migrations dumps into schema_info
doesn't seem to help at all. Anytime I run rake db:migrate, it wants to
run all the migrations. Also as a side effect, you can't rollback or do
much else.

I tried re-installing rake and that made no difference.

Is there a 2.1 setting in my 2.0.2 app that I missed?

Thanks.

Brandon Casci wrote:

I have a Rails app running under 2.0.2. I created the app with 2.1, but
eventually ran into some bugs and set the app to run at 2.0.2, and
commented out the 2.1 initializers.

Did you run rake rails:update?

Phlip wrote:

Brandon Casci wrote:

I have a Rails app running under 2.0.2. I created the app with 2.1, but
eventually ran into some bugs and set the app to run at 2.0.2, and
commented out the 2.1 initializers.

Did you run rake rails:update?

Not yet. I went back to too 2.1 for now, but I will try going back down
to 2.0.2 and updating config files.