On 6/30/06, Charles O Nutter <[EMAIL PROTECTED]> wrote:
FYI, once we're further along we'll probably be lobbying the Rails team to include the JDBC adapter in core :)

A related issue here is that it's not easy to package a new ActiveRecord adapter as a plugin AFAICT, since Rails::Initializer sets up the db before any plugins, so initialization fails if it can't find the adapter.  Some of the options I've come up with:

- package and distribute as a gem and manually set RAILS_CONNECTION_ADAPTERS before ActiveRecord is require'd
- same as above except distribute as a plugin; additionally you'd have to manually add the plugin lib directory to the load path ahead of time
- modify the initializer "config.frameworks" to exclude ActiveRecord during regular initialization, and then initialize ActiveRecord later.  This is what I'm doing currently; see http://tinyurl.com/g4no6 for details.

It would be nice if this "just worked" and didn't require additional configuration beyond the mandatory changes to database.yml.  Ideas appreciated!

Cheers,
/Nick
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to