Rails Ruby on Rails

Comments and changes to this ticket

• You flagged this item as spam.
  

  Damien MATHIEU June 24th, 2010 @ 09:39 AM

  Could you provide the entire backtrace ?
  You'll get it with rake db:migrate --trace

• You flagged this item as spam.
  

  Calum MacLeod June 24th, 2010 @ 09:49 AM

  c:\xampp\htdocs\church>rake db:migrate --trace
  (in c:/xampp/htdocs/church) Invoke db:migrate (first_time) Invoke environment (first_time) Execute environment Execute db:migrate rake aborted!
  Mysql::Error: query: not connected: CREATE TABLE schema_migrations (version
  varchar(255) NOT NULL) ENGINE=InnoDB
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connec
  tion_adapters/abstract_adapter.rb:221:in log'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connec<br/> tion_adapters/mysql_adapter.rb:323:inexecute'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connec
  tion_adapters/abstract/schema_statements.rb:109:in create_table'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connec<br/> tion_adapters/mysql_adapter.rb:477:increate_table'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connec
  tion_adapters/abstract/schema_statements.rb:369:in initialize_schema_migrations<br/> _table'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migrat<br/> ion.rb:441:ininitialize'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migrat
  ion.rb:401:in new'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migrat<br/> ion.rb:401:inup'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migrat
  ion.rb:383:in migrate'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rails-2.3.8/lib/tasks/databases.rake:112<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:incall'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in execute'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:ineach'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in execute'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:ininvoke_with
  call_chain'
  C:/xampp/ruby/lib/ruby/1.8/monitor.rb:242:in synchronize'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:ininvoke_with
  call_chain'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in invoke'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:ininvoke_task
  ' C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in top_level'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:ineach'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in top_level'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:instandard_ex
  ception_handling'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in top_level'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:inrun'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in standard_ex<br/> ception_handling'<br/> C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:inrun'
  C:/xampp/ruby/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
  C:/xampp/ruby/bin/rake:19:in load'<br/> C:/xampp/ruby/bin/rake:19

• 

  Rohit Arondekar June 24th, 2010 @ 10:06 AM

  I don't know if this is still relevant but you could try the solution provided in this blog post -> http://halyph.blogspot.com/2009/08/rails-23-migration-issues-with-m...

  If it does work please update this ticket so that it can be closed.

• You flagged this item as spam.
  

  Calum MacLeod June 24th, 2010 @ 10:15 AM

  I downloaded the older libmySQL.dll and put it in c:\xampp\ruby\bin as advised in the post mentioned by Rohit Arondekar.

  Then, I merely issued the "rake db:migrate" command once more and it worked, straight away.

  Thanks, Rohit and HalypH !

  Calum

  This ticket should now be closed.

• 

  Rohit Arondekar June 24th, 2010 @ 10:20 AM

  • State changed from “new” to “invalid”

  Cheers :)