This project is archived and is in readonly mode.
undefined method `new' for Rails::Configuration:Module when running rake db:setup
Reported by Zack Chandler | January 24th, 2010 @ 10:53 PM
~/dev/rails3testapp(master) $ ruby -v
ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-darwin10.2.0]
~/dev/rails3testapp(master) $ rake --trace db:setup
(in /Users/zackchandler/dev/rails3testapp)
** Invoke db:setup (first_time)
** Invoke db:create (first_time)
** Invoke db:load_config (first_time)
** Invoke rails_env (first_time)
** Execute rails_env
** Execute db:load_config
rake aborted!
undefined method `new' for Rails::Configuration:Module
/Users/zackchandler/dev/rails/activerecord/lib/active_record/railties/databases.rake:4:in `block (2 levels) in <top (required)>'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:636:in `call'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:636:in `block in execute'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:631:in `each'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:597:in `block in invoke_with_call_chain'
/Users/zackchandler/.rvm/rubies/ruby-1.9.1-p378/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/zackchandler/.rvm/rubies/ruby-1.9.1-p378/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:607:in `block in invoke_prerequisites'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:604:in `each'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:604:in `invoke_prerequisites'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:596:in `block in invoke_with_call_chain'
/Users/zackchandler/.rvm/rubies/ruby-1.9.1-p378/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2029:in `block (2 levels) in top_level'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2029:in `block in top_level'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2001:in `block in run'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/Users/zackchandler/.rvm/gems/ruby-1.9.1-p378/gems/rake-0.8.7/bin/rake:31:in `<top (required)>'
/Users/zackchandler/.rvm/rubies/ruby-1.9.1-p378/bin/rake:22:in `load'
/Users/zackchandler/.rvm/rubies/ruby-1.9.1-p378/bin/rake:22:in `<main>'
~/dev/rails3testapp(master) $
Comments and changes to this ticket
-
Scott Marshall January 25th, 2010 @ 02:29 AM
I ran into the same issue. I checked out a random commit from 1/23/10 and rake db:create worked. Must have been something done in the last day.
-
Ryan Bigg January 25th, 2010 @ 12:09 PM
It seems this has to do with the Engine additions. Rails::Configuration is now Rails::Application::Configuration but simply changing it over in databases.rake does not fix the issue.
-
-
Ryan Bigg January 25th, 2010 @ 12:46 PM
And another with a suggestion from snusnu to use Rails::Application.instance.config instead.
-
Martin Gamsjaeger (snusnu) January 26th, 2010 @ 02:27 AM
I think this can now be closed. See http://github.com/rails/rails/commit/64f8c87b1dab9bc9b6324fd6a3d779...
-
Yehuda Katz (wycats) January 26th, 2010 @ 02:31 AM
- State changed from “new” to “resolved”
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Martin Gamsjaeger (snusnu)
Yehuda Katz (wycats)
Zack Chandler