On Wed, Jun 11, 2008 at 06:22:52PM -0700, Scott Bronson wrote:
>
> On Wed, Jun 11, 2008 at 5:58 PM, Matt Palmer <[EMAIL PROTECTED]> wrote:
> > If anything, this patch is anti-DRY because it locks up the database config
> > in a place that can only be read by Rails...
>
> The beauty of this patch is that now the database config can be read
> from anywhere.
>
> If you still want to read your config from a YAML file, nothing's
> stopping you. I presume you could do something like this:
>
> require 'yaml'
> db.merge(YAML::load(File.open('database.yml')))
>
> And it's just as easy to store your database config in XML, CSV, LDAP,
> or another database. Your deployment options are wide open. Really,
> this patch frees the database config. Where's the downside?
It's different to every piece of documentation that is already out there,
and it breaks Rails' motto of convention over configuration.
- Matt
--
"The user-friendly computer is a red herring. The user-friendliness of a
book just makes it easier to turn pages. There's nothing user-friendly about
learning to read."
-- Alan Kay
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" 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/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
