Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  Anil Wadghule May 11th, 2010 @ 07:27 PM

  Do you mean your 'mysql' host name is pointing to 'localhost' i.e. 127.0.0.1 ?

• You flagged this item as spam.
  

  Michael Hasenstein May 11th, 2010 @ 07:48 PM

  Yes.

• 

  Ryan Bigg May 13th, 2010 @ 11:47 PM

  • Tag set to “bugmash”
  • State changed from “new” to “incomplete”

  Please add further steps to reproduce this problem.

• You flagged this item as spam.
  

  Seivan May 15th, 2010 @ 12:51 AM

  Alright I tried to redo this

  127.0.0.1 mysql
  dscacheutil -flushcache

  rake db:create
  rake db:migrate
  rake db:populate

  all good so far.

  Post.all => [Post....]
  

  rake db:drop:all

  This task only modifies local databases. blogstain_development is on a remote host.
  This task only modifies local databases. blogstain_test is on a remote host.
  This task only modifies local databases. blogstain_test is on a remote host.
  Couldn't drop blogstain : #<Mysql::Error: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)>

  However
  rake db:drop works as intended.

  So, if you wanna deal with the other environments, just set it before dropping;
  RAILS_ENV="test" rake db:drop

• You flagged this item as spam.
  

  Seivan May 15th, 2010 @ 12:56 AM

  Argh, can't edit post.
  Thanks to NathanielJ from #railsbridge

  This piece of code gets called when doing a rake db:drop:all
  So.. basically it can't tell what addresses you got inside /etc/hosts :-)

  def local_database?(config, &block)
  

  if %w( 127.0.0.1 localhost ).include?(config['host']) || config['host'].blank?
    yield
  else
    $stderr.puts "This task only modifies local databases. #{config['database']} is on a remote host."
  end
  

  end

• 

  Rohit Arondekar May 15th, 2010 @ 05:43 AM

  This raises the question as to why the check => if %w( 127.0.0.1 localhost ).include?(config['host']) exists? Can somebody clear up as to why the remote db can't be dropped? One thing that comes to my mind is that most of the times the user of the remote db may not have permission to drop the entire db?

• 

  David Trasbo June 29th, 2010 @ 10:49 AM

  • Importance changed from “” to “Low”

  Rohit,

  I think it might be to stop people from accidentally deleting production databases. It's not something I know, though.

• You flagged this item as spam.
  

  Lenary July 30th, 2010 @ 10:51 PM

  It is indeed to prevent people destroying data on separate hosts. if it points at localhost, why can't you just have it as localhost?

• 

  Santiago Pastorino February 2nd, 2011 @ 04:34 PM

  • State changed from “incomplete” to “open”

  This issue has been automatically marked as stale because it has not been commented on for at least three months.

  The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

  Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:34 PM

  • State changed from “open” to “stale”

• You flagged this item as spam.
  

  bingbing March 26th, 2011 @ 01:29 AM

  gucci watches