On Wed, Jun 11, 2008 at 12:08:42PM -0500, Adam Keys wrote: > As the name of the patch implies, this approach is also considerably > DRYer. If you want, you can define everything in environment.rb and > move on.
I'm not sure how you're repeating yourself by putting the database config in a separate file. Where's the repetition? If anything, this patch is anti-DRY because it locks up the database config in a place that can only be read by Rails. If you've got anything other than Rails that wants to talk to the database (cron jobs, other apps, whatever) YAML is a far better way to store your credentials than a chunk of Rails code (it's not even plain Ruby, because you need umpteen lines of scaffolding to evaluate it and get the values out of it). Practically anything can parse YAML, nothing except Rails can parse Rails. I'm -1 on this patch because it'll almost certainly make my life harder trying to host apps that use this convention. - Matt -- "I invented the term object-oriented, and I can tell you I did not have C++ in mind." -- 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 -~----------~----~----~----~------~----~------~--~---
