I'm just curious why you find it to be a problem that it loads the environment?
On Jul 2, 8:18 pm, Dave Rothlisberger <[EMAIL PROTECTED]> wrote: > If my code tries to access the database at "compile time", e.g. > defining methods based on values in a table, the rake db:create task > fails: > > rake aborted! > #42000Unknown database 'xxx_development' > > Why does the db:create task need to load the entire application in > order to create the database, instead of just reading database.yml? > > I'm not the first to see this, > e.g.http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/... > > andhttp://www.ruby-forum.com/topic/154561 > > Cheers > Dave --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-core@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
