Wow, thanks, that sql console looks amazing! How come Heroku doesn't
fold this into its official tools?
Regarding using db:pull, maintenance, followed by db:push, that
technique was extremely troublesome for me in the past, probably
because my database is big, around 5 GB. When uploading on db:pus
Also check out
http://github.com/ddollar/heroku-sql-console
On Mon, Aug 2, 2010 at 9:15 AM, Jonathan wrote:
> Running database transactions through this remote console setup is
> iffy... It might work better to do a db:pull (ideally of just the
> tables you want to change), do the database maint
Running database transactions through this remote console setup is
iffy... It might work better to do a db:pull (ideally of just the
tables you want to change), do the database maintenance locally, and
then push the updated tables. You can put the site into maintenance
mode while you do this, if
That's how Heroku works -
http://docs.heroku.com/performance#request-timeout. A console command
is treated identically to a HTTP request.
Oren
On Sun, Aug 1, 2010 at 6:57 PM, Mike wrote:
> Okay, actually fixed this, sort of, by updating my heroku gem.
>
> Now it now longer crashes and just quit
Okay, actually fixed this, sort of, by updating my heroku gem.
Now it now longer crashes and just quits the console and tells me that
it's timed out and I should run it as a rake task instead of from the
console.
Overall behavior seems to be the same still, with the request
continuing to run on t
I'm updating some data in my database, and running them through the
Heroku console since we have no direct database access.
I'm calling this like so: ActiveRecord::Base.connection.execute "MY
SQL COMMAND;"
The command takes about 5-10 minutes to run.
Every time I run it, it's causing the console
