Did run rake db:migrate, still gives me pending migration error

Question

What is the right way to use the functions in migration, 'up' and 'down'?

I required some new column names to be settled. So I had destroyed the old controller and generated a new one, and a new model with some columns.

Later on I had replaced 'change' function name with 'down', rake, it all goes normal.

But I'm still confused that why a 'down' works.

I assume the situation is because there were some column names conflicting, so migration task couldn't happen. Rails thinks migration was not rake, that's why it gave me pending migration error, and it loops. And 'down' function in migration will be forcibly ran, to solve some type issues or columns conflicting(mine situation).

is this what part of 'down' works for ?

@davidrac I only changed the function name in migration and nuke it, problem solved. And then I get name back to "change", rake, nothing happened. — CoolDrinE, Sep 23 '15 at 10:49

score 0 · Answer 1 · edited Sep 23 '15 at 08:10

0

down is used for reverting migrations rather than error handling (your situation).

edited Sep 23 '15 at 08:10

ahmacleod

4,280
19
43

answered Sep 23 '15 at 06:42

X.Zeng

1

couln't I just rollback ? – CoolDrinE Sep 23 '15 at 10:50

Did run rake db:migrate, still gives me pending migration error

1 Answers1