Rails::Initializer should assure ERB is loaded before reading database.yml
Reported by José Valim | July 29th, 2008 @ 08:03 PM | in 2.1.1
I was trying to create an environment where only ActiveRecord was loaded, but since ERB is loaded by ActionPack, when reading and interpreting database.yml on initializer.rb, it raises an error.
To fix I just needed to add the line below to railties/lib/initializer.rb, on the database_configuration method (around line 700):
require 'erb' unless defined?(ERB)
So we have:
def database_configuration
require 'erb' unless defined?(ERB)
YAML::load(ERB.new(IO.read(database_configuration_file)).result)
end
Comments and changes to this ticket
-
Hugo Barauna July 29th, 2008 @ 09:53 PM
- → Title changed from “Rails::Initializer should assure ERB is loaded before reading database.yml” to “+1”
I also had to hack it myself.
-
Jeremy Kemper July 29th, 2008 @ 10:08 PM
- → Milestone changed from “2.x” to “2.0.3”
- → State changed from “new” to “open”
- → Assigned user changed from “” to “Jeremy Kemper”
- → Title changed from “+1” to “Rails::Initializer should assure ERB is loaded before reading database.yml”
-
Jeremy Kemper July 30th, 2008 @ 10:04 AM
- → Milestone changed from “2.0.3” to “2.1.1”
-
Repository July 30th, 2008 @ 10:07 AM
- → State changed from “open” to “resolved”
(from [af92dc53a830a4639d38df79048f1a30a89dd38a]) Initializer requires ERB explicitly instead of assuming Action Pack loaded it. [#722 state:resolved]
-
Repository July 30th, 2008 @ 10:08 AM
(from [c4038764d2b4c05178cceb22066e0ece59fe49d2]) Initializer requires ERB explicitly instead of assuming Action Pack loaded it. [#722 state:resolved]
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
Repository is at http://github.com/rails/rails
Check out the development master (Edge Rails):
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too"..
