On 6/26/07, Derrick Spell <[EMAIL PROTECTED]> wrote: > > Perhaps the answer would be to have rails load the > adapters as gems, but not have the gems installed along with rails. > You can load the proper adapter gem at the same time you load the > corresponding library gem, and then it's available to whatever project > may need or want it.
yes this makes sense, also something i didn't think about: probably the database adapter depends more in the machine environment than on the single application (as in: my development machine has the sqlite db and required gem, while my production machine ahs the postgresql database and gem installed) Luca --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
