# Rake db:migrate:redo

**URL:** <https://www.ruby-forum.com/t/rake-dbredo/142182>\
**Category:** Rails\
**Created:** [July 4, 2008, 8:16am UTC](https://www.ruby-forum.com/t/rake-dbredo/142182 "2008-07-04T08:16:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ole](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/fbc32d/32.png) [@ole](https://www.ruby-forum.com/u/ole)\
**Post date:** [July 4, 2008, 8:16am UTC](https://www.ruby-forum.com/t/rake-dbredo/142182/1 "2008-07-04T08:16:46Z")

</div>

rake --describe db:migrate:redo says:

```
Rollbacks the database one migration and re migrate up. If you want

```

to rollback more than one step, define STEP=x

Presumably that means, it runs #down and then #up. But I’ve put calls to  
Kernel#puts in both methods and it’s running #up first, resulting in  
“Mysql::Error: Table ‘posts’ already exists:”.

So I tried running these:  
rake db:drop:all  
rake db:create:all  
rake db:migrate  
rake db:migrate:redo

And it still does exactly the same thing!

It’s not a major issue, I can certainly work round it but this just  
seems weird. I’d like to know what’s going on. Rails version: 2.1.0

---

<div class="post-metadata">

**Author:** ![ole](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/fbc32d/32.png) [@ole](https://www.ruby-forum.com/u/ole)\
**Post date:** [July 4, 2008, 10:26am UTC](https://www.ruby-forum.com/t/rake-dbredo/142182/2 "2008-07-04T10:26:24Z")

</div>

I dont get that. I run down and then up.

i havent seen that happen before either…

sorry for the pesimism 🙂 but i just cant think what is wrong with  
your rakes…

On Jul 4, 7:16 am, Oliver S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![ole](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/fbc32d/32.png) [@ole](https://www.ruby-forum.com/u/ole)\
**Post date:** [July 4, 2008, 5:24pm UTC](https://www.ruby-forum.com/t/rake-dbredo/142182/3 "2008-07-04T17:24:00Z")

</div>

i have the same problem! if you find out a solution let me know!

On Jul 4, 8:16 am, Oliver S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![ole](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/fbc32d/32.png) [@ole](https://www.ruby-forum.com/u/ole)\
**Post date:** [July 4, 2008, 10:49pm UTC](https://www.ruby-forum.com/t/rake-dbredo/142182/4 "2008-07-04T22:49:41Z")

</div>

Bardo wrote:

> i have the same problem! if you find out a solution let me know!

Do you by any chance have only a single migration?

---

<div class="post-metadata">

**Author:** ![ole](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/o/fbc32d/32.png) [@ole](https://www.ruby-forum.com/u/ole)\
**Post date:** [July 5, 2008, 12:06am UTC](https://www.ruby-forum.com/t/rake-dbredo/142182/5 "2008-07-05T00:06:20Z")

</div>

Oliver S. wrote:

> Bardo wrote:
> 
> > i have the same problem! if you find out a solution let me know!
> 
> Do you by any chance have only a single migration?

Ahh try: gem update --system