Rails core - Jun 2006 - Pure-ruby adapters and future of JDBC adapter

I know there are pure-ruby adapters for various databases in Rails, maybe
even for all supported databases. We''re working to get Rails running
well
under JRuby, and since we obviously can''t use C extensions I would like
to
know where I can find pure-ruby adapters to play with.

We also, naturally, have our ActiveRecord/JDBC adapter, which is working
well, but it''s not entirely database-agnostic yet (ie the current impl
has
some MySQL-specific stuff in it we need to get rid of). The eventual goal is
that any JDBC database can be supported without customization or additional
adapters, but until we have that working I''d like to try out other
databases. That requires pure-ruby.

FYI, once we''re further along we''ll probably be lobbying the
Rails team to
include the JDBC adapter in core :)

Nick Sieger is the dev primarily responsible for the super-cool JDBC
adapter; he may add his comments to the thread.

Any help with pure-Ruby adapters or thoughts about future inclusion?

-- 
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ www.jruby.org
Application Architect @ www.ventera.com


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

On 6/30/06, Charles O Nutter <headius@headius.com>
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