The ActiveRecord-JDBC adapter is rapidly maturing these days. I got the full set of AWDwR2 migrations to run with it against MySQL last night, and Ola Bini has gotten migrations working well against Oracle and Firebird. We also have SQL Server support running most of our test cases (under non-Windows environments too!) and have started adding support for Derby and HSQLDB (Java-based DBs). Things are looking very good. However we have a very small request. In order for ActiveRecord-JDBC to be usable, users must manually modify the list of supported adapters in activerecord.rb, adding "jdbc" to the list. We would be very thankful if there were a way to include the "jdbc" string in that list in future releases. That would allow users to get up and running just by installing "rails" and "ActiveRecord-JDBC" gems, requiring no additional steps. I believe the currently-listed databases also have external requirements, so adding "jdbc" seems reasonable...especially since we''ll never need to add anything else; "jdbc" support covers all databases at once. Is this a reasonable request? Also FYI, we''d like to work with you folks to find a way to refactor out some of the DDL logic in the stock adapters so we can reuse it in the JDBC adapter. With JDBC we get very nice support for straightforward queries, updates, typing, and precision without any additional work, but there''s no facilities for generating DDL. This means that without us copying the core Rails DDL logic (as we''re doing now) or abstracting it out into a callable module (which we''d like), migrations would not work with the JDBC adapter. I''ll start a separate discussion on that once we''ve got some idea how it could look, but I wanted to let you know it''s coming. -- Contribute to RubySpec! @ www.headius.com/rubyspec Charles Oliver Nutter @ headius.blogspot.com Ruby User @ ruby.mn _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core