> In my opinion, those extra adapter should be distributed as gems. Installing > them as plugins should be discouraged because you have to repeat it for > every app. If you already chose to go with some non-mainstream db backend, > the chances are you'll be using the same for all your applications anyway. > > And if you're unable to install the gem at your web host, you can always > unpack it in "vendor/" or simply copy the gem file in "vendor/gems" after > this gets in: http://dev.rubyonrails.org/ticket/8511 > > So, when will the adapters be extracted? Are there known maintainers for > every one? Are they going to be in external repositories?
We have an active oracle maintainer, but the other adapters tend to float around from time to time. They'll be extracted before 2.0, and we'll need to run a maintainer hunt around that time. As for internal vs external repositories, I'd say that external repositories are the best option, but if it's a deal breaker for someone I'm sure we could carve out a repository here for them. Whether we choose gems or plugins for the adapters, there's some work needed to make sure that it works smoothly. At present the adapters are required very early in the initialization process, so hopefully someone who's maintaining / creating an adapter can help us get the required changes into AR. -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
