Heroku db:pull taps gem pulls previously db:push'd data instead of current data

Question

I'm using the taps gem, and I am trying to use heroku db:pull to pull down my current production database.

However, when I pull, it pulls down a database that I db:push'd almost 3 months ago, instead of the current DB.

Is there a way to specify that I want the latest? Is it possible to remove that old database?

Thanks for your time

EDIT: I'm using MySQL locally, and I am aware of pgbackups and am trying to avoid the pg dumping associated with that.

score 1 · Accepted Answer · edited May 23 '17 at 10:24

1

If you have multiple deployment environments (ie staging vs production), make sure you specify the right one with db:pull --app productionAppName.

If you have unused tables in the production environment that you want to get rid of, your two options are:

both techniques are described in this post: Heroku Drop Table Rails Help

hope it helps!

edited May 23 '17 at 10:24

Community

answered Aug 22 '12 at 20:40

ryan0

I do have multiple environments, and I am pulling from the correct one – rpearce Aug 22 '12 at 20:48

score 0 · Answer 2 · answered Sep 06 '12 at 16:23

0

There was only 1 DB on Heroku, but it had remnant tables from a long time ago that were not overwritten when I pushed the new database up.

TL;DR => it merged the old DB with the new

answered Sep 06 '12 at 16:23

rpearce

i had that same issue. i've edited my original answer and included the link i used to resolve it. do not go the manual route unless your db migrations are messed up. – ryan0 Sep 08 '12 at 20:48

2 Answers2