On Fri, Jul 4, 2008 at 10:39 PM, zilkey <[EMAIL PROTECTED]> wrote: > > I think loading the environment with db:create and db:drop is > unnecessary. I've run into scenarios where a plugin does some > initialization based on the database and raises exceptions if there is > no database (ultrasphinx and acts_as_ferret are two that come to > mind).
+1 on this comment, and I don't think this should be considered a plugin design flaw. This thread is like deja vu of the database.yml vs. environment config thread. I still believe that any *external* dependencies or resources (databases, gems) should get special treatment. In other words, if there is a dependency which is external to the app, any rails provisions for managing it should not be dependent on the app initializing first. Otherwise, it's a chicken and egg problem. That's why db:create should not depend on the app initializing, and also (shameless plug) why I'd prefer the GemInstaller (which has standalone as well as integrated invocation options) over config.gems for managing gems, including the Rails gem(s) itself :) -- Chad --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
