Rake migrate -- which db affected?

Rails
1

Dumb question, but when you do ‘rake migrate’, which database is
affected (e.g. test, development, or production)? Is there a way to
target a specific one?

Thanks,
Joe

2

Dumb question, but when you do ‘rake migrate’, which database is
affected (e.g. test, development, or production)? Is there a way to
target a specific one?

I believe that rake always runs in development mode, unless you redefine
RAILS_ENV to something else. A common pattern I use is something like

RAILS_ENV=production rake deploy

etc.

Best,

Danny

3

Hmm, would be nice if something like this was possible:

rake migrate --env=production

Joe

4

Looking at the wiki, it appears this is possible:

rake rails:freeze:edge REVISION=1234

So, perhaps this is also possible:

rake migrate RAILS_ENV=production

Joe

5

On Oct 9, 2006, at 7:12 PM, Joe R. MUDCRAP-CE wrote:

Hmm, would be nice if something like this was possible:

rake migrate --env=production

Joe

That would be nice but unfortunately rake tasks cannot take command
line arguments like that. THats why you have to use the RAILS_ENV hack.

-Ezra