Nah, that wouldn't work in this case unless the .my.cnf or the default mysql client config defined the correct place for the socket. Another thing that would work I think is if mysql is also listening on the tcp port then using "127.0.0.1" for the host instead of "localhost" would tell it to try to connect via tcp instead of through a socket.
So if the database.yml had development: adapter: mysql encoding: utf8 database: ReviewSite_development username: root password: host: 127.0.0.1 then just doing "heroku db:pull" would work On Mar 30, 6:41 pm, Adam Wiggins <[email protected]> wrote: > In addition to Ricardo's solution, I think another thing you can do is just > leave off the database url. You mentioned that you have a > config/database.yml, without specifying a URL it will read from that > automatically. i.e. > > $ heroku db:pull > Auto-detected local database: sqlite://db/development.sqlite3 > ... > > Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
